ARCADIA-Studio/harness/TASK_LEDGER.md

# Task Ledger — first release

Updated 2026-09-11 by Codex-9e8r6t `/root`. Release not accepted.

## Goal and success criteria

[PROJECT_GOAL.md](../PROJECT_GOAL.md), copied from attachment
`815ff7b9-73c4-41a2-a809-635ecf8389d6/goal-objective.md`, is authoritative.
Deliver a usable, substantially complete OA/SA systems modeling product in
Rust/Iced on Windows and Linux, with equivalent graphical/textual/REST editing,
strict reST semantics/API, arbitrary development-artifact traceability and
navigable offline help. Constraints/calculations, quantities/units and reusable
model libraries and complete uncluttered text-only small/large modeling are
explicit requirements. Later Arcadia layers remain future
releases. Completion requires real engineering tasks, sound semantics, relevant
passing checks and fresh independent cross-disciplinary review.

## Given facts

- User prioritizes Capella's domain capability and useful visual nesting while
  rejecting clutter, intrusive creation rows, static behavior diagrams and long
  homogeneous option lists. Reduce cognitive load in small and large models.
- Source must be understandable to engineers and AI, work with Git and preserve
  full parity. OA/SA transitions in both directions must be clear and reviewed.
- User authorizes autonomous reversible work, research, native Computer Use and
  parallel agents. Use GPT-6 Astra exclusively with task-appropriate effort.
- Gitea coordination and shared Wiki updates are required. Identify host and
  worker consistently and preserve overlapping work. Explicit project messages
  are authorized; unrelated external messages are not.

## Verified facts

[STATE.md](STATE.md) records exact commits, live leases and scoped verification.
The current model has one typed core, validated atomic commands and coordinated
Project/SourceBundle history shared by desktop and REST. Included files share
one global namespace. Current Constraint expressions are strings; numeric unit
strings do not convert values or establish dimensional compatibility. There is
no package/version/instance/update contract for cross-project libraries.

Candidate3 completed the main basic/transition/history/reopen story with exact
four/six-source independent model oracles; supplementary native cases remain.
Corrected immutable desktop631/631 passed; later Sensor correction passed53/53.
Final creation21/guide3 and matching full desktop653/653 passed after ancestry
label correction. StrictClippy/fmt pass after one behavior-equivalent history
let-chain rewrite; affected history63 and matching GUI build pass. Native named
creation passes complete model and 7/8/9-source oracles, individual Undo/Redo and
byte-exact nine-file reopen at actual minimum size. Cancellation preserves the
six-file baseline. Blank process/scenario canvases provide no useful first-action
prompt; this is an observed usability finding. SA draft recovery remains active. Mounted
layout tests establish pane geometry, not native task acceptance. Packaging checks
and independent review are scoped to supplied binaries/fixtures, not release
acceptance. Supported WSL2 import failed; a current Linux runtime is unavailable.

Current grammar supports omitted initial IDs/defaults, lexical ownership, forward
references and preserved source. Static audit found no exposed project-wide
reference navigation/alias refactor; current Find searches the active buffer.
The process example has128lines/14UUIDs/31empty-default lines, while meaningful
shorter source is possible. Two concise snippets passed26 real REST requests,
including identity-only normalization, exact name-only edits, rejected writes and
restart persistence. Counts and this small trial prove neither improved native
usability nor large-project performance.

## Assumptions

- Contextual named creation, remaining-height canvas and local source insertion
  can reduce actual authoring detours. Native engineer tasks must establish this.
- A bounded pure calculation/quantity model and pinned library content may fit
  the existing typed core better than a general-purpose metamodel rewrite.
  Independent designs and experiments must test this before ratification.
- Existing OA/SA semantics provide a useful foundation; neither their presence
  nor old acceptance proves full conformance to the updated release objective.

## Open questions

- Which precise calculation, quantity-kind/unit and library contracts satisfy
  practical budgets, reuse and update workflows without ambiguous defaults or
  implicit execution? How should they migrate and participate in transitions?
- Which behavior workflows still force cancellation/navigation to create missing
  context, and which local actions best remove those detours?
- Which text-only assistance best preserves engineering context and identity:
  native language services, external-editor services, source recipes or explicit
  reviewed patch operations? Which grammar changes are actually necessary?
- Does the new scenario pane remain readable and editable through actual native
  window sizes, camera changes, nested fragments and reopened caller contexts?
- Which viable Linux environment can run current GUI/server acceptance? Current
  VM limitation does not block remaining Windows, semantics or source work.

## Candidate designs and decisions

- Behavior creation: compact New → three task choices → focused name/owner/
  viewpoint card, explicit missing inputs, atomic creation and reserved recovery
  IDs. Implemented, reviewed and scoped native creation/history/reopen passed.
- Contextual prerequisite creation: stage an explicit typed source inside the
  current parent draft, then validate/adopt source and consumer atomically. This
  preserves intent and one-step history; a separate Architecture excursion or
  early source commit loses those guarantees. Initial Lifeline/process Work/
  machine-owner adapters and semantic first-action prompts are being implemented
  and independently challenged; acceptance remains pending. See the
  [bounded plan](release-contextual-source-creation-plan-20260911.md).
- Scenario workspace: compact header, optional Tools/Selection shelves, actual
  remaining-height canvas/form, pinned actions, independent scrolling and
  explicit Fit/Focus. Mounted tests support this choice; native proof pending.
- Quantities/calculations: compare additive pure analysis records, extension of
  existing fields and external evaluation. No broad schema decision yet.
- Libraries: compare copied source, live references, generic definition/usages
  and pinned typed packages with explicit mappings and reviewed updates.
  [Falsification brief](release-library-candidate-review-20260910.md) records
  identity, dependency, offline and conflict requirements. No ratified winner.
- Text authoring: use existing omission/default/identity contracts for concise
  experiments; compare source navigation/refactoring/patch assistance before
  grammar redesign. No namespace, hidden identity or omission change ratified.

Long-lived decisions remain in [DECISIONS.md](DECISIONS.md). New user scope and
normative contracts supersede older prototype exclusions.

## Current strategy

Finish coherent creation gates and test the rebuilt product against independent
saved-source oracles. Close remaining scenario lifecycle integration boundaries.
Use the native Capella study and independent criticism to address real authoring
friction. In parallel, resolve foundational semantic additions and text-only
authoring through bounded competing designs and executable experiments. Then implement all representations,
verify real REST and Windows/Linux workflows, build actual optimized packages
and conduct fresh end-state review. Do not weaken acceptance to match current
implementation or stop because a narrow technical milestone passed.

Pre-consolidation content is preserved byte-for-byte in
[the dated archive](history/2026-09-10-ledgers-before-second-consolidation/TASK_LEDGER.md).