Skip to content

Decision 0007 — Page Test Scripts, In-App User Wiki And Change History

  • Status: ACCEPTED
  • Date: 2026-08-15
  • Scope: every Logistics Workspace user-facing screen and page-owned sub-surface
  • Restriction delta: RD-000 / NONE

Decision And Current Application

Retain reproducible page-specific browser proof, in-app operational guidance, version-linked evidence and business/Process change history. The 2026-08-15 decision introduced these responsibilities so that source-only completion, decorative screenshots or Git logs could not replace operator acceptance. It did not make Wiki prose a business-policy authority.

The original blanket "every modification" wording and version/procedure lists are superseded in application by the current change-scoped update matrix. Unchanged internal moves do not require no-op scripts, articles or histories. This reconciles the existing later maintenance standard; it does not waive a selected Task's required acceptance.

Current operational requirements have one owner each:

Responsibility Current owner
Change applicability and durable documentation Documentation authority §8
Page script, scenarios, version parity, screenshots, history and completion evidence Quality Gates §10.1–10.4
In-app manual source, rendering, navigation and publication boundary Wiki README

The original decision text remains in Git history. Existing dated audit revisions/checksums retain their historical meaning; consolidation neither reruns evidence nor upgrades runtime acceptance.

Consequences

  • page changes are more expensive but verifiable and teachable;
  • tests cannot drift silently from screens;
  • screenshots are reproducible evidence rather than decorative captures;
  • users receive current instructions inside the system;
  • developers and AI can see why page logic changed;
  • missing runtime/wiki evidence blocks completion rather than becoming later cleanup.

Rejected Alternatives

  • generic shared browser test with no page-specific script;
  • static prototype screenshots as user-manual evidence;
  • detached README/manual files not rendered by the system;
  • updating test documentation without updating executable scripts;
  • relying on Git log instead of page-specific Process history;
  • hosted CI/GitHub Actions as the only enforcement path.

Rollback

Supersede this decision explicitly. Do not silently remove page scripts, User Wiki routes/content, evidence manifests or page histories while affected screens remain active.

---

Source: new-system/docs/decisions/0007-page-test-scripts-and-in-app-user-wiki.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.