Skip to main content

​
GreatBook completed build

🟢 Shipped in the GreatBook web application. The consolidated backend and frontend work is merged, including the later Matching W3–W7 completion and frontend integration. 🟡 Public MCP ingress and registry current; provider acceptance open. The pinned source and public OAuth/MCP descriptor carry registry 1.14.1 and the closed typed staged-domain adapters. ChatGPT and Claude behavior remains unexercised end to end.

​
Included workflow and surfaces

  • one canonical Transactions list in Ledger, with source, status, filter, journal-entry and workpaper drill-down
  • retirement of the redundant Journal list, with exact entry and legacy-tab links resolving into the owning Transactions event
  • a separate Books workspace for seven authoritative native subledger families, their registers, accounting links and control-account tie-outs
  • the Accountant Accounting Desk, including Close, Analysis, Allocations, Costing and Adjustments read surfaces
  • W1–W7 matching: bank evidence, scoped reads, idempotent decision writes, assurance residuals, workbench, Typewriter evidence handoff and document-chain facets
  • durable links among evidence, matching decisions, native records, accounting events, audit workpapers and exact journal entries
  • explicit loading, empty, partial, inconclusive, error and permission behavior rather than silent zeroes
  • protected Auditor browser access: conversational reads only; scheduled job mode and privileged scope remain server-owned
The build preserves existing accounting controls: fixed-point money, optimistic concurrency and idempotency on matching decisions, human-gated adjustment release, immutable posted entries and reversing corrections. The final source cut also adds exact-facts journal replay, paired control-account/native facts across the finance writers, exact loan base evidence, correct PIT-remittance and factoring semantics, signed inventory adjustments, shared Books/Close inventory truth, serialized Close certification, typed native business reversals and the 307-value document currency contract. Typed business reversal is deliberately narrower than a generic journal editor: the web product stages eligible posted events from Transactions, Close and posted Adjustments, and the typed MCP staging tool targets the same review flow. There is no dedicated reversal App, the live public MCP process is current on registry 1.14.1, provider behavior is unexercised, and only an exact confirmed selection can reach the canonical compensation service.

​
Included MCP capability contracts

  • 116 stable capability outcomes across 26 domains in the 1.14.1 release source, with product lifecycle, MCP-adapter availability, Apps resource and normal deep-link truth kept separate
  • 46 outcome records executable through 32 shared typed tools, distinct from the 50-tool release-source transport contract and 18 resources (17 MCP Apps plus the JSON skill registry)
  • progressive search/describe discovery, deterministic workflow recommendation and durable staged-workspace resume
  • typed staged commits for workflow resume, W3 Matching accept/reject/undo, Typewriter approve/submit, adjustment approve/reject, fiscal close/reopen and business reversal
  • exact target versions, server-derived organization/actor/roles, canonical revalidation, idempotency, maker-checker evidence and reversal/compensation declarations
  • explicit forbidden outcomes for generic SQL/HTTP/actions, raw finance writers, credential access and model-selected authority
Operational SOP retrieval now uses the deterministic Git-rendered in-process index; optional Clerk raw-intake text publication to Cognee remains a separate lane. These counts describe both the pinned source and live public MCP inventory at registry 1.14.1. They do not establish successful use through ChatGPT or Claude.

​
Deployment and validation

The GreatBook application repositories use a self-hosted GitHub Actions runner for repository validation and release automation. It is documented at this level only: it runs the repository workflows without exposing runner hosts, addresses, credentials or registration material. For this Mintlify documentation site, deployment is separate: the Mintlify GitHub App publishes main to docs.vinmake.com. There is no documentation-site GitHub Actions workflow and no Mintlify PR preview.