Release notes
Documentation changelog
Material changes to public product contracts, workflows, and security boundaries.
7 September 2026 — Improved record review and summary sharing
Compare the supplied records in either public example and share a review summary with missing evidence and next checks.
- Compare record sets in Public Demo v3 and inspect evidence locations and unresolved checks
- Restore a review summary from a link containing its selected conditions and pinned version
- Start from the supplied records and initial results on the homepage, then open an API request
- The examples use fixed synthetic records; they issue no real approval or customer environment access
4 September 2026 — Made the running public runtime explicit
The first public edition connects HARBINGER, PÓLYA, and RAIFFA to a running public GET endpoint and a verifiable current response rather than presenting the products as documentation alone.
- Equal public execution paths for corporate and financial record review and industrial supply-chain early warning, each ending in RAIFFA authority-requirement checks
- A synthetic Public Demo v2 in which the visitor chooses only the incident and the real GET API derives gaps and conflicts by comparing reference, time, and state across fixed source packs
- An execution-proof panel that reads the HTTP status, request ID, precomputed HARBINGER candidate, PÓLYA review paths, RAIFFA authority check, and same-input SHA-256 from the current response
- A guided mode, request-response console, failure paths, and a SHA-256 verification record bound to the resulting signals, gaps, review paths, and required authority route
- Response-derived counts showing where separate source checks, gap write-up, option framing, and authority discovery become one connected record
- A GET-only OpenAPI 3.1 contract for HARBINGER subjects, observations, changes, evidence, time, and gaps
- English-first documentation with an independently authored Korean edition and product-specific overviews, guides, examples, references, and boundaries
- Private Preview, security, legal, and support contact channels
- Markdown, OpenAPI, sitemap, llms.txt, and an RFC 9116 security contact file
Documented stop requirements for alternate observation paths
Published agent-incident investigations informed a control requirement that applies a stop to the subject, job, and trace—not only to one URL.
Record product meaning, not editing activity
We record changes to contract meaning, authority, access, security boundaries, or externally verifiable product artifacts. Copy, spacing, and color adjustments are not inflated into release events.