Synthetic local prototype
Tailbook
A synthetic lease-assurance workspace connecting aircraft evidence, transitions, and maintenance reserve review.
9T1 Labs / WebTailbook
- Categories
- Web / iOS
- Year
- 2026
- Role
- Creator
Premise
Connect the evidence chain without pretending to replace authority.
Tailbook links clause-to-evidence assurance, delivery and redelivery control, and maintenance reserve review in one synthetic workspace.
The command surface, API, and field companion share an auditable path while keeping legal, regulatory, airworthiness, registry, sanctions, accounting, and payment decisions outside the prototype.
Interaction
One evidence version moves through distinct human reviews.
Capture
A field inspector records a synthetic borescope package while offline.
The native companion preserves an offline inspection before synchronization. Synchronize
An idempotent request creates a new immutable evidence version.
Review
A named technical reviewer accepts or rejects the specific evidence version.
Transition
A separate reviewer records the return-condition decision.
Accepted means approved by the named reviewer for this workflow, not regulator accepted. Check
A finance checker reviews the reserve proposal without moving money.
System
Three surfaces share one typed workflow contract.
The current runtime is local and fixture-backed. The production target remains a modular monolith with explicit storage and connector boundaries.
Command surface
- React and TypeScript
- Action queue
- Evidence review
- Transition and finance views
Workflow API
- Versioned mutations
- Named actors
- Tenant checks
- Append-only audit events
Field companion
- SwiftUI capture
- Offline workspace
- Idempotent sync
- Conflict-preserving state
- Current store
- The demonstrated API uses deterministic in-memory fixtures and resets when it restarts.
- Production direction
- PostgreSQL row-level security, immutable object storage, quarantined documents, and outbox workers are specified but not implemented.
Boundaries
Every consequential term is evidence-bounded.
| Term | Meaning inside Tailbook | What it never means |
|---|---|---|
| Accepted | Accepted by a named reviewer for a stated workflow | Regulator accepted, compliant, or airworthy |
| Evidence current | The expected version and source date are present | The underlying fact is legally or technically conclusive |
| Checker approved | A separate role approved the proposal | Money moved or a settlement became final |
| Connector result | A mocked or external reference is visible | A registry, sanctions, or authority action succeeded |
Verification
The workflow was tested across web, API, and native surfaces.
Web and API
Type checks, production builds, route tests, workflow tests, origin controls, and browser review flows passed in the repository verification record.
Offline replay
The Swift core covers idempotent replay, stale-version rejection, and a disclosed-version retry against the local API.
Human control
Focus return, named actors, version checks, explicit empty states, and structured conflict messages were exercised in the final browser pass.
Still unresolved
Production work begins at the trust boundary.
Identity and tenancy
Production needs authenticated actors, tenant row policies, and expiring cross-organization grants.
Document safety
Uploads need quarantine, malware scanning, content normalization, isolated OCR, and human acceptance.
External systems
Registry, sanctions, ERP, e-signature, and payment connectors require contracts that never fabricate success.