Generating and regenerating
What Entalpa's AI drafts and when: what is added at once, what waits for your review, and what a lock protects.
What is drafted, and what waits for you
| Action | What happens |
|---|---|
| Create project | Drafts the stakeholders and the stories from your description, and from any files you attach, and adds them. |
| Generate, while there are no requirements | Drafts the requirements from your stories, and adds them. |
| Regenerate, once there are some | Proposes new requirements, rewrites and deletions. Nothing changes until you accept. |
| Analyze, on the requirements you select | Scores each one, and proposes a rewrite or its removal. |
| Propagate to requirements, on the Stories page | Drafts requirements from the stories you choose, as proposals. |
| Audit, on the Stories page | Proposes stories to add, change or remove. |
| Add Stories, its AI Suggest tab | Suggests missing features and the questions to ask a stakeholder. The stories you select are added. |
Each uses credits, from the balance beside your name. Generate and Regenerate also work on one subsystem: see Subsystems and propagation.
Reviewing what is proposed
Proposals open in a review: Generated Requirements Review or Requirements Analysis for requirements, Backlog Audit Review for stories. Each change shows beside what it changes. Take it, adjust its fields first, or reject it. In a requirements review, Accept All leaves deletions out, for you to select yourself; in the backlog audit, it takes every change, deletions too.
- Proposals are saved with the project. Close the review and come back to it from Review suggestions in the Requirements toolbar, or from the Overview.
- A proposal whose target was edited since it was made says so: applying it overwrites those edits.
- Accepting is one step to undo, and undoing it puts the proposals back up for review.
Locks
Lock a requirement with the lock in its row of the requirements table. Regenerating leaves locked requirements as they are, though the model still reads them, and accepting a proposal never changes one: a proposal for a locked requirement stays in the review until you unlock the requirement or decline the proposal.
A lock binds the AI, not people
A lock does not stop a direct edit: you, a teammate or a coding agent can still change a locked requirement.
For experts: from needs to requirements
Stories are the stakeholders' needs, and requirements say what the system must do to meet them. ISO/IEC/IEEE 15288:2023 keeps the two apart as processes, stakeholder needs and requirements definition (6.4.2) and system requirements definition (6.4.3), and the INCOSE Needs and Requirements Manual describes turning one into the other. Generating drafts that step with AI, and the review keeps a person deciding what goes in.
Research agrees that the person is needed. A systematic review of language models in requirements engineering (Hemmat et al., 2025) found that their mistakes, invented content among them, call for manual correction and careful oversight, and named validation by a person in the loop as the way forward.
Where Entalpa departs from these sources, it says so:
- The first draft goes in without review. Create project, and Generate while there are no requirements, add what they draft at once: there is nothing yet to overwrite, and Undo takes it back. From then on, nothing changes until you accept.
- A lock is not a baseline. It keeps the AI's proposals off a requirement, but people and agents can still edit it. To fix the spec as it stands, save a version.
References
- ISO/IEC/IEEE 15288:2023. Systems and software engineering: System life cycle processes.
- INCOSE (2024). Needs and Requirements Manual, revision 2.0. INCOSE-TP-2021-002-01.
- Hemmat, A., Sharbaf, M., Kolahdouz-Rahimi, S., Lano, K. and Tehrani, S. Y. (2025). Research directions for using LLM in software requirement engineering: a systematic review. Frontiers in Computer Science 7, 1519437.