[ AxiomCore · Documentation ]
Advanced patterns
Combine shared form rules, typed failures, read caching, bounded streams, transactions and sandboxed computation, and verify each on your target.
Use these patterns once a small app such as the task app or exam app works on your target. Each pattern names the boundary you still have to verify, because a passing compile does not prove the behavior on every host, SDK or database.
Patterns
| Pattern | What it does | Boundary to verify |
|---|---|---|
| Shared form rules | Inherits selected validation, parses drafts, and maps approved failures to fields | Private rules and payload fields stay outside the selected contract |
| Logical submission identity | Keeps one runtime-owned key for a dispatched submission and its resolution | Do not store the key as a preference or invent a second body key |
| Authenticated read caching | Reuses bounded reads within the declared authority partition | Permissions, tenant and principal identity, invalidation, provider replay safety |
| Managed persistence | Writes business data, a submission receipt and an outbox event in one supported transaction | Qualified PostgreSQL profile, readiness, explicit grants, least-privilege tenant policies |
| Signed sandbox normalization | Passes only a title to a typed TypeScript, Rust or Python guest | The exact signed module, interface and authority; no implicit I/O, credentials, snapshots or host handles |
| Bounded snapshot streams | Reads an authenticated complete snapshot, reduces it, then closes the subscription | A finite snapshot is not a continuous change feed or a resumable event history |
| Typed read batching | Combines distinct authorized reads through a declared batch provider | Per-item outcomes and one physical dispatch; no implicit frontend HTTP merging |
| Receipt-backed archive batches | Persists a bounded event batch with a stable receipt | Database commit and Redis delivery acknowledgment recover separately |
Compose the application explicitly
- Keep the backend, frontend and database manifests separate.
- Select the public contract and the approved failure fields for each audience.
- Keep preference state apart from form drafts, submission identity and credentials.
- Make each successful mutation invalidate the queries that depend on it.
For receipt-backed PostgreSQL task data, IDs can be positive canonical decimal strings within the supported signed 64-bit storage range. Shared regex rules must stay within the portable subset. Browser preview checks do not establish native receipt and outbox atomicity, Redis admission durability or row-policy readiness; those need real provider and recovery tests.
Verify each execution layer
| Check | What it establishes |
|---|---|
| Compiler and contract check | Accepted syntax, types, selected rules and artifact compatibility |
| Reference or generated-adapter scenario | Scripted transport, ownership, assertions and cleanup on that runner |
| Mounted web or native application | Real target interaction and lifecycle behavior |
| Real provider integration | Persisted writes, replay and rollback behavior, configured isolation |
Preparing a project must not activate a provider, grant authority or contact a deployment. Review signed database readiness, credentials, sandbox bindings and grants explicitly before you serve real traffic.