Books Design Examination

Scope and Authority

All existing design artifacts and the Books responsibility row were examined against the pinned service and console sources. The examination compared the available planning layer without editing it. The named brief is absent, and planning records still carry draft status; this examination does not confer product approval.

The examination read declarations, persistence, guards, migrations cited by those declarations, route permissions, console resources and the cited consumers. Locked installed dependencies were inspected to verify generated health names and the scheduler behavior hidden behind package imports. Architecture citations to absent Platform standards remain unverified.

Counts and Coverage

Subject	Examined coverage	Limit
Design artifacts	52 of 52: five objects, five state models, eleven workflows, two services, fourteen screens and fifteen decisions	All received independent OpenAI final wording.
Responsibilities	One Books module row and its surrounding explanation	Other module ownership was not redesigned.
Invariants	38 structured invariants	Enforcing layers distinguish request checks from lasting database protection.
States and transitions	28 states and 45 transition rows	Nine external Platform transition outlines remain unknown.
Workflows	53 anchored hops across eleven flows	Cross-module effects are bounded to the cited readers and handlers.
Service operations	89 of 89: 81 business HTTP operations, two generated health routes and six internal lifecycle operations	Every row declares access, permission, planning realization and Submissions exclusion.
Physical storage	25 of 25 module tables and one view mapped to five objects	Three vocabularies are global; the external workspace table is read-only and not counted as owned storage.
Screens	14 of 14 resource or dedicated screen surfaces; 61 action rows	The editor contract covers new, existing and edit route variants. Products and Transactions retain ownership of their embedded actions.
Queues and scheduling	One schedule queue, its dead-letter queue, minute dispatch and six registered work kinds covered by the scheduled-work workflow	The generic mechanism does not prove exactly-once handler execution.
State machines	Scheduled posting initiation is covered by the scheduled-work workflow; provisioning, purge and export participation each have a workflow	No standalone state machine is declared by Books or maintenance. Referenced posting machines and Platform orchestration belong to their owners; an unposting ARN is supplied but no examined scheduled handler starts unposting.
Inference	All 27 service, workflow and screen contracts retain empty inference lists	No model task call was found in scoped implementations or the registered deterministic handlers, so no inference artifact is needed. The missing charter sentence remains an existing finding outside the permitted edit scope.

Every structured repository source and hop anchor was opened and checked for existence and support. The final audit contains 227 source and anchor rows; literal code and test anchors resolve, screen operation references map to declarations, and unknown-transition references point to their finding.

Storage Coverage

Object	Tables or view mapped
DOM-ACC-BKS-001	business_units, business_unit_currencies, exchange_rates, currencies; business_units_v view
DOM-ACC-BKS-002	gl_accounts, business_unit_default_gl_accounts, default_gl_account_purposes, bank_accounts, merchant_accounts, payment_processors, departments, accounting_projects, tax_rate_accounts
DOM-ACC-BKS-003	fiscal_years, fiscal_periods
DOM-ACC-BKS-004	document_templates; built-ins remain code content without a table
DOM-ACC-BKS-006	payment_terms, payment_methods, tax_classes, tax_zones, tax_rates, tax_rate_classes, settings, schedules, schedule_runs

The five active objects match the five active planning concepts by permanent number. The superseded payment-setup concept is covered by the workspace definitions and does not require a separate object. Business-unit registration declares no custom-field capability, and the other configuration requests provide no supported custom-field payload.

Changes by Artifact

Verification corrections were committed before final wording. Each artifact’s OpenAI rewrite was committed separately, with later source and wording refinements also recorded. Identifiers, field names, source pins and machine bindings were preserved except for the verified changes enumerated in structured report metadata; added transitions and screen actions retain existing artifact identities.

Artifact	Examination result and final-text changes
DOM-ACC-BKS-001	Creation atomicity, later calendar removal and request-time fee checks now have separate limits; ownership and omitted-field handling are explicit.
DOM-ACC-BKS-002	Removed false service currency immutability; retained unit and code protection, enabled-currency checks, restricting references and last-writer default assignment.
DOM-ACC-BKS-003	Separated calendar maintenance from Close standing; retained commit-time shape checks and the service-only latest-open-year deletion guard.
DOM-ACC-BKS-004	Distinguished built-ins, customer content, reference-derived usage and resolver guarantees; recipient limits apply separately to copied and blind-copied lists.
DOM-ACC-BKS-006	Replaced exactly-once execution with unique history-row identity, limited secret checks to recognized patterns and described staff availability exceptions.
STATE-ACC-BKS-001	Inactive creation is observed, with creation guarantees distinguished from later calendar deletion.
STATE-ACC-BKS-002	Period standing remains Close-owned and year standing derived; calendar extension does not perform a period transition.
STATE-ACC-BKS-003	Added inactive creation and clarified reference-based in-use standing, built-in protection and active duplication.
STATE-ACC-BKS-004	Added ended-schedule deletion and invalid-definition pause; disabled schedules do not cancel already claimed work, and unfinished runs can repeat.
STATE-ACC-BKS-005	Marked all nine Platform transition outlines unknown; retained observed Accounting availability and uncached purge guards without inventing Platform completion rules.
WF-ACC-BKS-001	Corrected the client refresh anchor and kept initial calendar creation in the unit transaction.
WF-ACC-BKS-002	Separated currency reconciliation, omitted fee preservation, template validation and the accounting-method read race.
WF-ACC-BKS-003	Distinguished preflight dependencies from actual restricting-key refusal and limited useful translation to recognized constraints.
WF-ACC-BKS-004	Described provider read before persistence, concurrent reference failure and conflict-skipped dated quotes.
WF-ACC-BKS-005	Kept generation explicit, horizon-bounded and atomic; extending coverage does not replay failed scheduled occurrences.
WF-ACC-BKS-006	Retained the historical payable-mapping disagreement and added the explicit deduction from soft rate references and replacement identities.
WF-ACC-BKS-007	Limited resolver adoption to observed producers and kept statement divergence open; selection itself has no persistence effect.
WF-ACC-BKS-008	Corrected duplicate execution, the publication crash gap, acknowledgement on recorded final failure and separate post-commit posting start; rewrote the failure branches in the diagram.
WF-ACC-BKS-009	Provisioning is one conflict-safe bulk insertion rather than a partially committed five-step seed.
WF-ACC-BKS-010	Separated bounded guarded Accounting purge from Platform continuation; earlier committed removal is never restored.
WF-ACC-BKS-011	Corrected staging-setting semantics, creation-cutoff limits, embedded collection handling and repeatability of location rather than values.
SVC-ACC-BKS-books	Verified all eighty rows, corrected the generated health name, mutable account currencies and default-write exceptions, and rewrote every intent and publication reason.
SVC-ACC-BKS-maintenance	Verified all nine rows, corrected the generated health name, scheduler failure semantics, conditional staging protection and posting-start boundaries.
SCR-ACC-BKS-001	Recorded inactive creation, default inactive filtering, immediate status changes and conditional multicurrency confirmation.
SCR-ACC-BKS-002	Removed nonexistent availability and bulk patterns; manual-only editing, provider filling and deletion remain.
SCR-ACC-BKS-003	Recorded the unit-specific defaults drawer, console-only type filtering and currency locking, and version-free purpose writes.
SCR-ACC-BKS-004	Distinguished the editor’s currency lock from service replacement and retained descriptive bank-only storage.
SCR-ACC-BKS-005	Retained disconnected processing, processor filtering and preservation of Reconciliation fields without implying a processor connection flow.
SCR-ACC-BKS-006	Specified the shared department side panel, fixed code and unit, required name and actual list patterns.
SCR-ACC-BKS-007	Specified optional project naming and informational end date with shared list and side-panel behavior.
SCR-ACC-BKS-008	Replaced generic list patterns with the dedicated fiscal page, expandable periods and generation, rename and delete dialogs.
SCR-ACC-BKS-009	Recorded the console’s whole-day restriction separately from fractional service support.
SCR-ACC-BKS-010	Retained immediate availability changes and bulk status actions without deletion, with system-method refusal enforced by the service.
SCR-ACC-BKS-011	Mapped address testing to Transactions and retained the missing historical-payable warning as an open limitation.
SCR-ACC-BKS-012	Added Products-owned default assignment and clearing actions and recorded the update-versus-delete permission mismatch.
SCR-ACC-BKS-013	Specified kind tabs, built-in protection, immediate availability changes and the settings-controlled statement default.
SCR-ACC-BKS-014	Specified the dedicated editor, inline initial-load failure, debounced preview retention, route variants and distinct permission gates.
ADR-ACC-BKS-001	Removed exclusive-writer and instant-visibility claims; shared reads depend on isolation and assigned writing responsibilities.
ADR-ACC-BKS-002	Narrowed universal versioning to replacements and documented omission exceptions and version-free purpose assignment.
ADR-ACC-BKS-003	Removed false account-currency protection and changed broad design intent from confirmed to proposed while preserving the narrower product origins.
ADR-ACC-BKS-004	Changed broad design intent from confirmed to proposed; the cited approval establishes unit deletion, not every collection’s observed behavior.
ADR-ACC-BKS-005	Described absent custom-field registration as observation without inventing product rejection or export requirements.
ADR-ACC-BKS-006	Retained explicit Submissions exclusions with proposed alternatives, not newly approved intake decisions.
ADR-ACC-BKS-007	Cited the settled posting-time destination decision instead of deciding it again.
ADR-ACC-BKS-008	Limited rollback to the current database transaction and retained provider delete-and-fill correction.
ADR-ACC-BKS-009	Retained explicit calendar extension and derived standing with the cited product origin.
ADR-ACC-BKS-010	Kept Commerce transfer and payable preservation open without inventing readiness of an external replacement.
ADR-ACC-BKS-011	Separated occurrence identity from handler repeat safety and retained unresolved Billing timing ownership.
ADR-ACC-BKS-012	Limited lifecycle guarantees to bounded participant work rather than Platform orchestration or universal recovery.
ADR-ACC-BKS-013	Kept shared selection behavior separate from producer adoption and product approval of inactive-content refusal.
ADR-ACC-BKS-014	Removed unproved absence of external demand and universal lack of reaction; the observed limitation is no change-event or revision contract.
ADR-ACC-BKS-015	Scoped row security to customer tables and explained global vocabularies and narrow dispatcher policies.
RESP-ACC	Aligned the Books row with both service contracts and five objects; removed universal version, deletion and execution guarantees while retaining delegated ownership.

Findings and Decisions Still Needed

Finding or question	Remaining decision or limit
FND-ACC-BKS-050	Supply the missing brief if it is authoritative and confirm the intended planning baseline.
FND-ACC-BKS-051	Review planning guarantees that exceed creation-time calendars and request-time fee-product checks.
FND-ACC-BKS-052	Obtain the owning Platform lifecycle contract before treating its transition outline as established.
FND-ACC-BKS-053	Screen contracts now describe the observed patterns; this is not approval of a new visual design.
FND-ACC-BKS-054, FND-ACC-BKS-055, OQ-ACC-BKS-006	Decide duplicate-handler safety and recovery of committed but undelivered claims.
FND-ACC-BKS-056, OQ-ACC-BKS-007	Choose whether export promises a stable snapshot or current values read over time.
FND-ACC-BKS-057	Broad observed configuration choices remain proposed unless a product origin establishes their full scope.
FND-ACC-BKS-058, OQ-ACC-BKS-008	Decide whether account currency changes should be consistent across clients.
FND-ACC-BKS-059	Align the product-type clear control with the service’s delete permission.
FND-ACC-BKS-036, OQ-ACC-BKS-005	Preserve payable destinations when rate configuration changes after tax is issued.
FND-ACC-BKS-037	Settle whether the accounting-method switch needs protection against concurrent posting.
FND-ACC-BKS-038, FND-ACC-BKS-042	Shared reads and complete document-resolver adoption still need their owning-module contracts.
FND-ACC-BKS-044, FND-ACC-BKS-045	Platform standards remain unavailable; locked-library behavior is now examined, while the charter’s no-inference sentence is outside this job’s scope.
FND-ACC-BKS-049	The earlier missing-symbol objection is resolved: the pinned export dispatcher is executable.
OQ-ACC-BKS-001 through OQ-ACC-BKS-004	Tax transfer, fee override scope, shared default warnings and configuration history remain open.
FND-ACC-BKS-023, FND-ACC-BKS-048	Billing timing ownership and a visible scheduling-pause notice remain unsettled.

Ten findings and three open questions were allocated before writing. Canonical padding of the newly allocated finding numbers was corrected without changing their numeric allocation. Existing planning text and identifiers were not modified.

Validation

The required clean dependency installation, corpus check and test command passed. Conformance reports zero errors, and all four repository checker tests pass. Service, integration and browser tests were inspected for provenance and anchors; this documentation job did not execute those application suites or deploy any service.

The final change set is limited to the authorized design, findings, registry, report, responsibility and module-status locations. The module status records examination rather than approval. Commits remain on the task branch for platform publication; nothing was pushed.

Verdict for Andrew

The examined design faithfully describes observed configuration and maintenance behavior at the pinned revisions, with unproved Platform transitions explicitly unknown. Its weakest areas are scheduled delivery guarantees, historical tax payable mappings and export consistency. Before implementation preparation, Andrew should confirm the planning baseline and decide scheduled repeat safety and claim recovery, tax transfer and mapping preservation, export consistency, and the remaining history and ownership questions.