# Next assignment: Maintain the completed system handbook

## Completed writing scope

All 85 registered topics have reviewed detailed answers. The original twenty
and the four authorized passes (16 + 19 + 14 + 16) are complete. Preserve the
stable IDs, exact questions, article kinds, canonical owners and old summary
anchors. There is no fifth writing pass. editorial/roadmap.md retains the frozen
65-topic partition; COVERAGE.yaml owns current topic status and relationships.

Writing completion is separate from implementation, deployment, current runtime
observations and independent product acceptance. Do not close an acceptance issue
or label a business workflow verified because the handbook is complete.

## Maintenance objective

When implementation, an accepted decision or operational method changes, update
the affected canonical answers and their contextual links in the same delivery.
For a standalone maintenance session, identify actual changes since each affected
article's source revision, then review one coherent set of dependent contracts.
Do not manufacture a new writing backlog, refresh every source pin without review
or repeat unchanged provider/business checks merely to obtain a newer date.

## Resume and choose the maintenance scope

1. Read AGENTS.md, docs/handover/current-status.md, docs/MAP.md, AUTHORING.md and
   the editorial structure/style/review-status pages. Check live GitHub issue/PR
   state and git worktree list. Continue the handbook branch only while its PR
   is open; after merge use current main and a new branch.
2. Compare current owning contracts, code, active migrations and tests with the
   specific article references. Check current public API/frontend versions only
   when making a deployment claim. A source revision is not runtime proof.
3. State the changed rule or concrete uncertainty and its canonical owner. Use
   CONTEXT.md for vocabulary and ADR status for authority. A proposal is not an
   accepted decision. Consult Estate/Dotiverse before adding a reusable platform
   mechanism; this maintenance assignment creates no such implementation mandate.
4. Update the real detailed answer, not only counters or metadata. Preserve its
   kind/question and negative boundaries. Move an address only with preserved
   summaries and all affected register/content/browser links updated.
5. Replace this assignment only with another self-contained maintenance scope
   when actual work remains. Keep the 85-topic completion statement accurate.

## Cross-area checks to preserve

- Exact actor/company/resource authority, customer company/person pairs, direct
  project versus customer-wide authority and stronger recipient/completion rules.
- Commercial validity/publication, request-to-accept and execution/review states,
  plus the documented UE audience, closure and photo limitations.
- Native eligible time-attestation autoqueue versus excluded imported approvals;
  receiving-payroll/PAX acceptance and the inactive direct connector boundary.
- Allocation/payment/credit source identity and coverage, report amount definitions,
  missing dates/currencies and deferred revised margin definitions.
- The 27-rule import reconciliation registry, replay identity and private-corpus
  evidence limits. Cleanup, replacement imports and operational cutover remain
  separate authorized outcomes.
- Mail originals/attachment coverage, bounded AI context, public MCP audience,
  bearer and quota limitations, free-text diagnostic paths and absent universal
  retention schedule. Do not silently claim these resolved.
- Exact-candidate publication, shared locks, source preservation, schema ledger
  versus catalogue, immutable forward migrations and forward-only writer failure.
- Health/readiness/heartbeat/version scope, independent monitoring and record-level
  outcomes. Canary skips cannot become proof of normal background processing.
- Generation-bound recovery. Component database/Storage receipts do not establish
  combined application/Auth/credential/decryption recovery. RPO 60 minutes and RTO
  240 minutes remain objectives unless a named measured scenario establishes them.

## Concrete outstanding decisions and evidence

Check current issue state before work. At the final writing review, the financial
lifecycle (#414), self-cost/margin definition (#375), complete working day (#413),
transition ownership/historical parity (#415), recovery/detection (#416), PAX
receiving outcome (#450), approved-time handoff (#395) and historical exceptions
(#159) retain distinct scope. Fixture cleanup (#409), environment transition
(#466) and the parent independent-operation outcome (#350) are not completed by
this handbook. The live issue owner and canonical contract take precedence over
this dated inventory. Record a concrete missing decision/scenario rather than a
new general audit. Existing receipts remain immutable evidence of their named
version and target.

## Execution boundaries

Documentation maintenance normally needs no shared provisioning, private mailbox
read, provider call, application restart or database restore. Bounded corrections
of established defects remain authorized by the task's working agreement: prove
negative and positive behaviour, check, publish affected components where required
and verify the actual result. Do not infer speculative redesign or data repair.

Shared functional checks use Vi Målar on app/api.toolora.se with established saved
sessions. Vi Målar is bound to real Fortnox company 1160465. Never test final
attest/export/send or payroll-queueing approval there. The DEV Fortnox company
1026975 has no bound tenant at the writing review. Do not change bindings, add
direct provider calls, run cleanup/replacement imports or restore shared data to
make a documentation check pass. Automated DB/reset/seed tools discover only their
own local/disposable stack target, never an ambient database URL.

Commands requiring shared configuration on AX42 run as dev with toolora-secrets,
using the exact identity/umask contract in AGENTS.md. Use the installed broker and
current backup service only when separately required by an actual schema release.
Keep secrets, personal data, private graph context and live payloads out of Git,
logs and distribution artifacts.

## Verification and delivery

Use Node 24 and worktree-owned dependencies. Run npm ci, npm run verify,
npm run test:browser and npm run package in docs/system for a clean committed
candidate. The final baseline checks all 85 canonical questions, sources, local
links/assets and content reachability, preserves the four-pass partition, and
exercises summaries, canonical routes, cross-area navigation, diagrams, mobile
matrices, A4 print, search and local-only browser runtime. Keep those assertions.

Inspect the complete diff and run make ci-plan BASE=origin/main plus the relevant
shared checks. Reuse previous executions only after proving relevant inputs
identical; report reused and fresh results separately. Record actual CI checkout
and source/artifact commit, especially when the combined merge tree includes
newer main files. Read failed steps before retrying. Do not dispatch duplicate
full CI or weaken required checks.

Push the first commit and use one draft PR while editing. Mark ready after local
review/checks, then resolve selected candidate CI to green. Build a versioned ZIP
from a clean commit; independently verify membership/hashes and the extracted
HTML through the README's local Python HTTP-server path. Retain older delivered
editions. Record commands, commit, archive/hash and concrete limits in the PR;
remove the delivered worktree and retain the branch while its PR is open.
The public online edition is https://docs.toolora.se/. Follow HOSTING.md to
publish the exact checked archive and verify HTTPS, search, assets and version
without changing application releases. A new audience/destination or combined
PDF remains a separate deliverable.
