Goal
Required before the proposal can be reviewed.
MINDBURN LABS
Request Company AI OS ReviewGeneratedSpecs
GeneratedSpecs are source-backed proposals, not execution.
A GeneratedSpec is a draft plan with sources. It cannot run anything until approved and routed through the HELM boundary. Engineering specs also need repository evidence before code work can close.
Define GeneratedSpec
- GeneratedSpec
- A draft work plan made from sources. It is not approved yet.
- Code Intelligence Graph
- A read-only map of code files, symbols, routes, calls, tests, and impact.
- CodeIndexReceipt
- A receipt that records which repo, commit, parser, files, and hashes were indexed.
- CodeImpact
- A source-backed report of changed files, affected symbols, routes, tests, and risk.
Required shape
Every spec must make review and proof clear.
The schema names what a reviewer needs before the draft can become an approved action.
Non-goals
Required before the proposal can be reviewed.
Source evidence
Required before the proposal can be reviewed.
Affected systems
Required before the proposal can be reviewed.
Read set
Required before the proposal can be reviewed.
Write set
Required before the proposal can be reviewed.
Acceptance criteria
Required before the proposal can be reviewed.
Test plan
Required before the proposal can be reviewed.
Risk class
Required before the proposal can be reviewed.
Required approvals
Required before the proposal can be reviewed.
Target connectors
Required before the proposal can be reviewed.
Execution plan
Required before the proposal can be reviewed.
Receipt requirements
What must be recorded if the approved action runs.
Engineering specs
Code work needs graph-backed scope before execution.
Required code evidencebefore closure
| Requirement | Why it matters |
|---|---|
| Pinned repository commit and source repo | Prevents engineering work from outrunning repository reality or approved scope. |
| Fresh Code Intelligence Graph index | Prevents engineering work from outrunning repository reality or approved scope. |
| CodeIndexReceipt reference | Prevents engineering work from outrunning repository reality or approved scope. |
| CodeImpact report with impacted symbols, files, routes, and affected tests | Prevents engineering work from outrunning repository reality or approved scope. |
| read_set, write_set, assumption_set, and route/API review scope | Prevents engineering work from outrunning repository reality or approved scope. |
| Rollback or compensation plan | Prevents engineering work from outrunning repository reality or approved scope. |
| Closure diff comparison against the approved write_set | Prevents engineering work from outrunning repository reality or approved scope. |
Reject or escalate
Missing code evidence blocks executable engineering specs.
Code Intelligence Graph evidence informs review. It does not authorize execution, and stale or missing evidence fails closed.
No repo commit is pinned
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
No fresh code index exists
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
write_set is missing
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Risky change has no affected tests
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Generated code touches forbidden paths
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Public route or API change lacks review
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Impact radius exceeds policy limits
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Actual diff exceeds the approved write_set
HELM returns DENY or ESCALATE according to policy before the work can execute or close.
Sample spec
A GeneratedSpec is a review packet, not a command.
Release-note correctiondraft only
| Field | Example content |
|---|---|
| Goal | Update the release note so the customer promise matches the shipped behavior. |
| Source evidence | Customer commitment, release ticket, merged PR, and test run. |
| Risk class | Customer-facing communication; approval required before publish. |
| Execution plan | Draft issue, update release note, request reviewer approval, then publish through approved connector. |
| Receipt requirements | Record approval, policy verdict, changed artifact, and proof pointer. |
Boundary
Review comes before side effects.
GeneratedSpecs organize goals, evidence, affected systems, approvals, connector targets, code scope, tests, rollback, and proof needs.
They cannot bypass review, PEP, CPI, approval, simulation, CodeImpact evidence, or receipts. Approved action still crosses the fail-closed HELM boundary.
Define boundary terms
- PEP
- The boundary that enforces the decision before a tool call runs.
- CPI
- The check that validates a plan before HELM lets it continue.
- Code Intelligence Graph
- A read-only map of code files, symbols, routes, calls, tests, and impact.
- CodeIndexReceipt
- A receipt that records which repo, commit, parser, files, and hashes were indexed.
- CodeImpact
- A source-backed report of changed files, affected symbols, routes, tests, and risk.