How the book is built
FORGE is how the book is built
The motto is FORGE: Connect, Orient, Run, Gate, Evolve. That is the sequence we run on every licensed book, so a stale private mark cannot look current and a late custodian file cannot silently drop out of a pack.
F
Connect
Define the problem worth solving and the data that exists
O
Orient
Mapping, dated marks, and recon flags
R
Run
Print the pack from the same book. Do not rebuild it.
G
Gate
Staged rollout with human-in-the-loop controls and monitoring
E
Evolve
Ongoing monitoring, drift detection, and capability
F — Phase 1
Connect
Problem Definition
Separate custodian positions from private marks. Do not blend them into one unmarked number.
Data Audit
Confirm which custodians you already receive and which files arrived, with the as-of date still attached.
Success Criteria
Quantified definitions of what good looks like, agreed before architecture decisions.
Feasibility Assessment
Technical and data feasibility validation with a clear go/no-go recommendation.
O — Phase 2
Orient
Architecture Design
System design with explicit tradeoffs documented and reviewed with client engineering.
Mark
Check private marks against the date entered. A stale mark stays stale on the pack.
Integration Mapping
API contracts, data flows, and integration points with existing systems documented.
Compliance Review
Regulatory and security requirements mapped to architecture decisions before build begins.
R — Phase 3
Run
Architecture Design
System design with explicit tradeoffs documented and reviewed with client engineering.
Mark
Check private marks against the date entered. A stale mark stays stale on the pack.
Integration Mapping
API contracts, data flows, and integration points with existing systems documented.
Compliance Review
Regulatory and security requirements mapped to architecture decisions before build begins.
G — Phase 4
Gate
Architecture Design
System design with explicit tradeoffs documented and reviewed with client engineering.
Mark
Check private marks against the date entered. A stale mark stays stale on the pack.
Integration Mapping
API contracts, data flows, and integration points with existing systems documented.
Compliance Review
Regulatory and security requirements mapped to architecture decisions before build begins.
E — Phase 5
Evolve
Architecture Design
System design with explicit tradeoffs documented and reviewed with client engineering.
Mark
Check private marks against the date entered. A stale mark stays stale on the pack.
Integration Mapping
API contracts, data flows, and integration points with existing systems documented.
Compliance Review
Regulatory and security requirements mapped to architecture decisions before build begins.
Pack alerts
Get pack alerts by text
Enter a mobile number to receive promotional texts when a household pack is ready. Message frequency varies. Message and data rates may apply. Reply STOP to cancel, HELP for help. Consent is not a condition of purchase.
