ROADMAP
Roadmap
The whole build in five phases, with a duration on every piece of work and on every phase.
The renewal book, the vessel archive and compliance, on one platform
Development
We publish each piece of the platform as it is finished, and we state what it does not do alongside what it does.
13/10/2026 COMPARISON TOOL
Checked every comparison figure against the clubs' own documents
We checked every figure the P&I club comparison tool took from a secondary source against the clubs' own documents, so that 884 now cite the club itself, 238 of them with a corrected value, and 115 that no document states are marked N/P instead of zero.
09/10/2026 COMPARISON TOOL
Made every figure in the comparison tool traceable and printable
Every chart in the P&I club comparison tool can now be opened with its figures, exported, or printed on its own as an A4 PDF, a figure a club does not publish now reads N/P instead of being left blank, and the figures for a single club now reach back to 2018/19.
05/10/2026 COMPARISON TOOL
Rebuilt the club comparison tool on the clubs' published figures
The P&I club comparison tool now has its own address, comparison.ajgmanifest.com, and runs on the 12 International Group clubs' own published figures for 2020/21 to 2025/26 in place of the illustrative figures it carried in September, with the document and page cited for every figure.
01/10/2026 SECURITY
Adopted audited cryptography for the key layer
We stopped designing the mathematics of the key layer ourselves, took it from one audited library, built the key evaluation and the refresh of the pieces on it, and put the sessions around them through an adversarial review that found two critical faults, both fixed, though no key service is running yet.
27/09/2026 SECURITY
Found that our key services had no way to agree
Our key specification assumed throughout that the five key services agree with one another and never said how; counted properly there are 23 places where they must, and the work ended with requirements, no design and nothing built.
23/09/2026 SECURITY
Adopted a published construction for the key design
We attacked our own key design twice and it failed twice, so we went looking for whether the problem had already been solved. It had. The method we had arrived at was published in 2019, and the architecture page now cites it by name.
17/09/2026 DATA MODEL
Settled how the book is stored
Eight decisions now fix how every renewal record, every document and every fact about a ship is held, together with what happens when somebody asks to be erased. These are design decisions rather than built ones, and they are the ones everything else will sit on.
09/09/2026 VESSEL IDENTITY
Settled how every vessel is identified
Every ship in Manifest gets one permanent identifier that carries no meaning, and a separate set of rules decides which ship a new record belongs to. We checked both against a large body of real vessel particulars before settling them.
04/09/2026 DATA INTAKE
Built the document ingestion engine
The document reader is built and every specimen document now reads. To prove it reads rather than remembers, we rebuilt the corpus with different vessels, parties and figures and ran it again.
29/08/2026 DATA INTAKE
Researched and planned the document ingestion engine
How Manifest will read certificates, invoices and commission notes, and why every figure it reads will show its working.
25/08/2026 VESSEL IDENTITY
Designed the permanent vessel identifier
Every vessel carries three references, one of them fixed for the life of the hull.
21/08/2026 SECURITY
Designed the security core
No key is stored anywhere, and withdrawing a broker's access is a single write.
17/08/2026 PLANNING
Planned the platform and the infrastructure
The platform was specified in full before any code was written, item by item.
