> ## Documentation Index > Fetch the complete documentation index at: https://docs.vinmake.com/llms.txt > Use this file to discover all available pages before exploring further. # Verified release status > What the current GreatBook release proves in source, and what remains unverified in the running product. # Verified release status This page separates shipped code from exercised product behavior. A merged route, component, migration, or test establishes that a contract exists in the release; it does not establish that a person has completed that workflow in production. ## Release identity | Component | Verified release | | ----------------------- | --------------------------------------------- | | GreatBook backend | `3c17397e120e91bda33d4bbb55d8963d82a17ba7` | | GreatBook web | `057bc2f535bd1d9e55f3244acf301f6fae8e8d08` | | Database migration head | `0068_adjustment_note_proposals` | | Capability registry | `1.14.1`, evidence cut `2026-08-11T00:00:00Z` | The generated registry contains 116 records across 26 domains: 98 current, seven experimental, one queued, two deprecated, and eight forbidden. Forty-six records are available through 32 typed MCP adapters within the 50-tool, 18-resource transport contract. Those counts match the live public MCP inventory, but they are not proof that an external MCP client or every web workflow has been exercised. ## Public MCP boundary The live public documents at `https://greatbook.co/.well-known/oauth-protected-resource` and `/.well-known/mcp.json` establish an OAuth-protected Streamable HTTP ingress at `https://greatbook.co/mcp`. The public MCP descriptor advertises registry `1.14.1`, matching the pinned backend and web release. The authenticated production Capability Browser renders `Registry 1.14.1 · evidence cut 2026-08-11` with all 116 of 116 records. ChatGPT and Claude behavior through that ingress remains unexercised. ## Verified in the release | Area | What the source establishes | Delivery boundary | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Capability browser | `/dev-center/capabilities` searches the release registry, shows lifecycle and delivery separately, and never invokes a capability. | Its API fails closed when the bundled and deployed registry identities cannot be reconciled. | | Posted-entry reversal | An eligible immutable journal can produce a durable reversal proposal; a different named person must approve the exact plan before the compensating entry and native compensation post atomically. | The web uses the proposal-specific review route, not the generic staged-workspace flow. Production currently has only one bound identity, so the two-person path is unusable there. | | Credit and debit adjustment notes | Migration `0068` and `AdjustmentNoteProposalService` require a discrepancy basis, an attributed proposal, and a distinct named approver before the note and journal post together. | The engine control is present; no public end-to-end adjustment-note workflow is claimed here. | | Close binder | The read-only Accounting binder page requests one period-scoped package, preserves declined evidence, and downloads the exact response bytes. | Registry `1.14.1` still marks `greatbook.close.binder.read` experimental and blocked. | | Master maintenance | Typed item and employee proposal, review, and approval routes call the existing domain writers and retain proposal and approval evidence. | The registry marks the master capabilities experimental and blocked; employee pay, cost allocation, and employment status are outside this boundary. | | Analysis attribution | Accounting Analysis reads canonical journal-event detail and keeps complete, partial, missing, inconclusive, and error attribution distinct per line and dimension. | An omitted attribution object is not reinterpreted as “missing.” | | Exact-money reads | The shared read authority rejects non-finite or binary-float money and publishes fixed-point decimal strings with an established currency basis. | A malformed successful response is unavailable, not rounded or treated as empty. | | SOP retrieval | Clerk and operational explanations use the Git-rendered in-process SOP manifest with deterministic, scoped lookup and content hashes. | This path has no network, embedding, model, credential, or mutable remote index. Optional raw-intake text publication to Cognee is a separate lane. | | Consolidation authority | Effective-dated group membership, immutable entity identity, server-bound read grants, and the `ws_group_reader` RLS boundary exist in migration `0060`; the group reader withholds incomplete populations. | Group reports are gross member contributions with no eliminations and are experimental/blocked in registry `1.14.1`. | | Actions | `/actions` has server-filtered lanes for `ready_for_review`, `waiting_confirmation`, and all runs, and opens the exact linked workspace for a person's decision. | It lists only staged work linked to a workflow run; directly staged record work is not covered by the collection read. | | Books | All seven native family routes are represented, and missing source facts or a missing as-of clock remain `partial`, `inconclusive`, `error`, or freshness unavailable. | The UI withholds counts and all-clear claims when the response cannot support them. | ## Deliberately not claimed as working The following paths are present in code but have not been verified end to end for this release: * Chat; * the intake review queue; * Typewriter; * the Actions decision flow and other staged actions. The two-person reversal path is deployed but is not usable in production today. Its control correctly needs two distinct named people, while production currently has only one bound identity; no reversal was attempted by weakening that control. The authenticated production Capability Browser confirms the signed-in catalogue version and all 116 records. That verifies registry parity and inventory, not successful use through ChatGPT or Claude. ## Read next * [Capability lifecycle and anti-drift](/greatbook/greatbook/capability-registry) * [Typed business reversals](/greatbook/features/business-reversals) * [Actions decision queue](/greatbook/features/actions-inbox) * [The seven Books families](/greatbook/features/books-families) * [The local SOP index](/greatbook/agents/sops)