Income note fixture
fixture://income-note.pdf · synthetic digest · illustrative / specimen / not checked
Read the record before asking a qualified person to act. This workstation is a proposed Epic 25 shell specimen.
The shell preserves evidence, policy context, a qualified human boundary, and a server-owned receipt contract as distinct stages.
Tenant and purpose remain explicit.
Source, derivative and limits stay separate.
No module supplies a lending outcome.
Receipt shape only; no durable write here.
Two synthetic review requests
Frozen illustrative snapshot. No eligibility, pricing, affordability, or underwriting conclusion is shown.
Illustrative observation only. A cited policy context can guide review; it never makes a lending decision.
fixture://income-note.pdf · synthetic digest · illustrative / specimen / not checked
fixture-ocr/0.0 · page 1 · recorded region · illustrative / specimen / not checked
An operator selects a scoped request, reads the original source and derivative limitations, inspects cited policy context, then asks a qualified human to review. A durable receipt follows only a valid server-owned outcome.
A domain vocabulary layer over the stable Allura shell. It contributes typed intake labels, evidence vocabulary, policy references, and stage presentation—but no browser code or authority.
Curate the context around a request without granting a module independent authority.
Evidence, policy, and requested human handoff are inspectable together.
Inspect source provenance and OCR derivatives before reading a policy observation.
Illustrative provenance record; no document is loaded.
fixture://income-note.pdf · synthetic digest · fixture upload
fixture-ocr/0.0 · page and region retained · derivative only
MR-4.2 specimen bundle · evidence citation required
Inspectable receipt shape for the Epic 25 UI walkthrough. It never represents a server-issued decision.
Epic 25 keeps one stable enterprise shell. Third-party SDK participation is later and remains proposed / illustrative.
First-party signed candidate
Illustrative admission state
Scoped state is illustrative
Not part of Epic 25
First-party, declarative workflow labels, typed intake, evidence vocabulary, cited policy references, and shared-service bindings.
Out of baseline. No marketplace, arbitrary client-side plugin, or independent trust model is proposed here.
A shared review packet for a qualified human — never automated underwriting, eligibility, pricing, or a lending decision.
Typed fields and opaque evidence references only.
Collects typed fields and evidence references; it has no decision tool.
Shows provenance, OCR confidence, cited observations, and limitations.
Cowork or Dashboard may request handoff to Allura’s review workspace.
Only an authorized person in Allura may decide; the shared service records the receipt.
Govern enablement and operating posture through typed, auditable settings — not arbitrary module configuration.
Lifecycle specimen with explicit host controls.
Every value is a proposed specimen. Effective settings inherit down through the scoped shell and retain their resolution chain.
Platform default → organization → workspace → resource/module binding
Approved first-party module IDs; workspace may narrow but never weaken an organization boundary.
Host API, runtime, platform, release channel, signature, and revocation acceptance rules.
Typed shared capability intersection for the module version and scoped audience.
Retention, residency, legal hold, and access-aware display obligations.
Administrator-approved reference only; the module cannot set an outcome.
Append-only history, read access, export governance, and supersession links.
The governed control plane beneath the product surface: fail-closed boot, database-enforced policy, deterministic replay, measured evaluation, and a second governed pipeline. Every figure resolves to a committed evidence artifact.
The gateway refuses to start without authentication; a health gate then proves the stack is live. A missing token cannot silently disable the control.
Row-Level Security is enabled and forced, so it applies even to the table owner — the difference between a real control and a decorative one.
Replaying a recorded receipt re-executes the scenario and compares every field.
Run through real executors against PostgreSQL as a NOBYPASSRLS role — the lanes can fail, which is what makes them evidence.
latency moves run to run (8ms → 7ms) — a fixture can’t; a falsifiability suite feeds each lane inputs that should fail and asserts they do.
Supply-chain threat intelligence, read-only and default-off. It ingests, batches, and either promotes a complete batch or holds a partial one with a stable reason code — nothing reaches exposure without passing the same gate as memory.