Skip to content

Documentation coverage

All 20 system areas have source-reviewed overviews or topic summaries. The register contains 85 topics with reader questions, article types and current addresses. The original twenty detailed topics and all four completion passes are reviewed: 85 of 85, with zero topics remaining at summary depth. The final pass adds all sixteen infrastructure, delivery, operations and decision/evidence topics. The four-pass plan preserves the original 65 assignments. Writing completion is separate from independent business acceptance and the concrete evidence limits recorded in each area.

The table is generated from COVERAGE.yaml. Detailed review counts refer to topic writing, not to application test results. Each page identifies its own review scope and source revision in the source details.

Source-reviewed overviews and all 85 detailed topics. The four authorized completion passes are complete; independent product acceptance and operational evidence retain separate scope.

Product source baseline: 6abe424a43c5.

AreaDetailed topics reviewedRemaining depth
Purpose and boundaries4 / 4Independent working-day and financial acceptance remain scoped to their own evidence.
Landscape and architecture5 / 5Declared configuration is not a current component/schema/provider-health observation; no universal endpoint or package audit is claimed.
Domain model and vocabulary4 / 4Arbitrary order restoration/reparenting and concurrent project-close guarantees need separate evidence. Organization contact creation retains email matching; contact profile and membership editing uses separate transactions. Presentation hashes cover selected facts, not a complete concurrent source freeze; publication metadata is not an immutable event history and there is no standalone presentation unpublish route. Source reconciliation labels do not establish native signer identity; independent contract-backed change-order workflows remain unverified.
Identity, companies and authorization6 / 6MCP resource-audience validation is disabled and incoming bearers are reused downstream; advertised identity scopes are not required business permissions. MCP metadata and business gates differ; exhaustive runtime issuance/revocation remains unverified; named same-token actor checks are recorded in the November 17 release. MCP quotas are non-atomic and fail open on count errors; full interface/effect coverage remains separate. Worker API/browser/RLS predicates differ; assignment and publication are not universal action gates. UE project-file audience filtering, closed-commitment authority and submission photo/scope ordering require separate policy decisions or verification. Customer discovery/detail now share paired live SQL admission; direct-project contact and customer-wide operation authority remain separate. PR 653 owns local SQL/Auth/list/revocation evidence; this handbook update does not establish shared deployment or exhaustive concurrent outcomes. API/SQL actor eligibility and token context now share a live projection; path-specific resource scope and exhaustive revocation remain separate. Exhaustive live revocation and concurrent company-switch outcomes remain unverified; the release receipt records its named context checks.
End-to-end business workflows4 / 4New-version and duplicate copies use separate requests; concurrent/recovery guarantees are not transactional. Generic view, decline and change-request gates differ from named/acceptance active-version enforcement. Website status push delivery remains deferred; financial acceptance in issue 414 remains separate from source review. Project invoice creation is transactional but has no general caller-key replay; operational payment summaries do not establish complete settlement. Public applications, qualification checks and commitment close are not one transaction; targeted response replay differs from application recovery. Checklist/assignment validation and order completion are separate operations; project completion has no transaction-wide barrier against new evidence. Worker corrections use a direct insert; UE review and customer delivery acceptance have different persistence and readiness contracts.
User interfaces4 / 4The inspected Storybook matrix and named receipts do not establish every device, screen reader or full working-day outcome.
Frontend implementation4 / 4Representative query/mutation review is not an exhaustive proof of every cache-key dimension, editor recovery path or runtime API shape.
API and application services4 / 4Route metadata and representative negative tests do not certify every resource check or provider outcome; HTTP payload/error contracts remain operation-specific.
Data model and database4 / 4Selected record families are reviewed; a complete field/index dictionary remains outside this concept. Representative RLS paths are reviewed; shared live actor rules and path-specific API/SQL, portal and worker resource differences remain explicit. Selected transaction boundaries are reviewed; a complete function/trigger catalogue remains outside this reference. Migration preparation/release is source-reviewed; this delivery performs no shared release or current backup/restore certification.
Files, documents and communication4 / 4Representative Storage and signed-link paths are reviewed; UE projection/upload-order limits and per-flow cleanup differences remain explicit. Conversation audiences are reviewed; company inbox, resource-based portal, SQL message and Storage predicates remain distinct. Originals and intake are source-reviewed; actual mailbox coverage and provider delivery remain separately evidenced.
Finance and reconciliation6 / 6Independent deduction/credit/payment and receiving-payroll acceptance remain scoped to their open evidence; new cost/margin definitions are deferred.
Integrations and shared services4 / 4Shared contracts and representative accounting/mail/recovery paths are source-reviewed; current enablement and external outcomes need named evidence. Invoice-write connector adoption remains incomplete; unknown submissions and source gaps retain operation-specific recovery.
AI, assistant and MCP4 / 4Interface, context, proposal and governance contracts are source-reviewed; model correctness and live client/provider acceptance remain separately evidenced. MCP audience/bearer limits and non-atomic fail-open call quotas remain explicit.
Background work and change feeds4 / 4Declared schedules, representative outcomes, change cursors and stalled-work diagnosis are source-reviewed; deployed flags and individual business completion need separate evidence.
Import, history and data quality4 / 4Private-corpus parity, current historical exceptions and operational transition need scoped evidence; this review performs no import, cleanup or baseline rewrite.
Security and information handling4 / 4No universal retention schedule or automatic redaction of every runtime log is established; the documented MCP audience/bearer/quota and source coverage limits remain.
Infrastructure and runtime4 / 4Adoption proposals are not completed cutovers; source-declared topology and current host observations remain separate evidence.
Development, testing and delivery4 / 4Selected CI and component checks do not establish independent product/provider acceptance; schema publication requires its own exact candidate and fresh prerequisites.
Monitoring, diagnosis and recovery4 / 4Combined application/identity recovery, recurring proof and measured RPO/RTO remain open; component restore receipts retain their generation-bound scope.
Decisions, limitations and system status4 / 4Financial, working-day, transition, payroll, recovery and source/security outcomes retain their current owners and independent evidence requirements.

The next assignment maintains implementation changes, canonical links and evidence limits. There is no fifth writing pass. The completion plan records all four passes.