1
You supply the container
Markdown, Word, a section list, a template spec, or a PDF example. A PDF is lower confidence and always confirmed before it is frozen.
Carbon / Artifacts
A signed package, not a chat. A corporate SRS, client RFP, or submission layout wins. System templates are the fallback.
Request a trialRequirements
BRD / PRD / SRD
System requirements in an EARS pattern, cited to the charter or a constraint.
Security
Threat model
Written with the requirements, not assembled the week before an audit.
Compliance
Evidence
Only the standards you checked. Overlap resolves into one build. Cues.
Trace
Traceability
Need to requirement to constraint to diagram to screen. Always emitted.
Risk
Risk register
Residual risk stacked across the standards in play, with an owner where the template asks.
Shape
Architecture
Context, container, sequence, and data-flow from the same run. Not a separate drawing exercise.
Screens
Wireframes
Low-fidelity specs bound to system requirements, so a screen has a home in the specification.
Record
Audit trail
Hash-chained approvals, edits, rejections, and rewind reasons.
1
Markdown, Word, a section list, a template spec, or a PDF example. A PDF is lower confidence and always confirmed before it is frozen.
2
Carbon drafts the section list, including boilerplate it will keep verbatim. You approve or edit it at the intent gate. No silent merge.
3
IDs follow the scheme you declared. Empty required sections are reported. You choose a placeholder, a re-run, or a logged empty section.
Not promised
Headings, numbering, and boilerplate stay. Exact typography, complex tables, and brand assets do not.
If you bring no template