Work is organised by Target
A Target is a regulator-facing work package: a Stage 1 application, a business plan, a submission checklist, or a regulatory response. One Elevator instance can carry several Targets at once.
Each Target has its own priority and workflow stage:
discovery → convergence → composition → refinement → assembly.
The integrator proposes movement; a user confirms it.
Targets owe Deliverables
A Deliverable is the concrete artefact the Target must produce. It may be prose Elevator drafts, a file somebody else must supply, or an evidence pack assembled from existing material.
Deliverables have owners, deadlines, blockers, requirement coverage, and a derived status. The status follows the underlying work; it is not a manually coloured label.
Requirements make the obligation atomic
Regulator text is decomposed into Requirements: one verifiable claim per row. Each claim is routed to the Deliverable that will clear it.
That routing is the coverage contract. It answers a harder question than “did we write a document?”: which artefact proves or addresses every obligation?
Truth enters through sources and people
Documents supply quotable substrate. Evidence pins a fragment of a Document to a Requirement. Where the corpus is silent or contradictory, a Question asks a human for the missing truth.
A submitted answer first joins the UserInput queue. During the next round it is
preserved verbatim, analysed, and followed by a fresh readiness judgement. An answer informs
the work; it does not magically turn itself into documentary evidence.
Ready material becomes Drafts
Document-shaped Deliverables are composed through Sections. Once the architecture is confirmed and enough Requirements are ready, the Draft composer produces versioned prose.
Every Draft declares which Requirements it covers substantively and which remain explicit placeholders. Generated prose never becomes its own evidence.
Refinement has two loops
Internal feedback is captured in Elevator's editor as structured diffs and comments. External counsel works in Word: annotations become ReviewItems, grouped into a ReviewCycle with replies, amendments, a sync checklist, and verification.
Both loops preserve the connection back to requirements and sources while the wording changes.
Assembly ends in handoff, not autopilot
Elevator produces target and deliverable manifests, drafts, evidence and coverage views, checklists, compilation snapshots, review history, and a clear account of remaining blockers.
The result is a review-ready package that legal counsel can inspect, package, and submit. Elevator does not impersonate counsel or the regulator's submission system.
Follow-ups choose the smallest useful shape
A small regulator or counsel follow-up can be an input, question, issue, upload, or review item. If it becomes a real work package with its own requirements and output, it becomes a short-lived transitive Target and travels through the same stage discipline.
Elevator remains a project-completion workspace. It does not drift into open-ended compliance monitoring.