Add named behavior creation and verified textual authoring examples
This commit is contained in:
+89
-180
@@ -1,199 +1,108 @@
|
||||
# Task Ledger — first release
|
||||
|
||||
Updated 2026-09-11. [STATE.md](STATE.md) owns current execution/evidence;
|
||||
[PLAN.md](PLAN.md) owns capability milestones. The entire former Task Ledger is
|
||||
[preserved byte-for-byte](history/2026-09-10-ledgers-before-continuation-refresh/TASK_LEDGER.md).
|
||||
Its old goal references, aggregate test claims and stopped-session directives retain
|
||||
historical scope. New semantic decisions are recorded explicitly in DECISIONS.md;
|
||||
prototype results retain their separate scope.
|
||||
Updated 2026-09-11 for Codex-ytr83r. The full
|
||||
[user goal](../PROJECT_GOAL.md) and [current progress](STATE.md) remain authoritative.
|
||||
[Exact host ledger archives](history/2026-09-11-ytr83r-integration/README.md)
|
||||
preserve prior facts, dates and reasoning without transferring their acceptance.
|
||||
|
||||
## Goal and success criteria
|
||||
## Goal and given requirements
|
||||
|
||||
Deliver the usable, feature-complete OA/SA first release specified in
|
||||
[PROJECT_GOAL.md](../PROJECT_GOAL.md). It is the exact copy of the user's revised
|
||||
`a49d1780-25d5-4778-ad68-6140c60e4207/goal-objective.md`, SHA256
|
||||
`DD58F75C93D55FE16ED141A23D834898FB6EBC625AE7E7AE379DA552A8312435`.
|
||||
|
||||
Success requires coherent explicit semantics, practical engineering workflows,
|
||||
equivalent graphical/textual/REST behavior, real Windows/Linux runtime evidence,
|
||||
recoverable authoring, relevant automated evaluators, precise documentation,
|
||||
reproducible packages and fresh independent cross-disciplinary end-state review.
|
||||
No known blocker or high-impact finding may remain unresolved. Later Arcadia
|
||||
layers remain future scope. Code, a passing slice or an attractive screen alone
|
||||
cannot establish completion.
|
||||
|
||||
## Given facts
|
||||
|
||||
- Rust/Iced desktop and a deployable REST service serve system engineers. OA/SA
|
||||
transitions in both directions must be understandable, explicit and useful.
|
||||
- The revised goal explicitly requires constraints/calculations, quantities/units,
|
||||
reusable model libraries, state/behavior modeling and strong standardized
|
||||
specification/API, as well as textual/graphical notation and artifact traceability.
|
||||
- Human/AI/Git-friendly source and a concrete unambiguous reST specification must
|
||||
match graphical editing. The source editor needs highlighting/linting; help must
|
||||
be offline, concise and navigable.
|
||||
- The newest explicit goal requires uncluttered notation that reduces cognitive
|
||||
load and supports development of complete small and large models using text alone.
|
||||
- Direct behavior/scenario diagram authoring and reduced cognitive load are current
|
||||
priorities. Long homogeneous selectors and bloated persistent creation controls
|
||||
are rejected. Study actual Capella's useful domain workflows and nesting without
|
||||
mechanically copying its interaction problems.
|
||||
- The user authorizes autonomous bounded engineering, native Capella/Studio
|
||||
evaluation and explicit independent delegation, exclusively with GPT-6 Astra
|
||||
at effort appropriate to the question. Root owns synthesis/integration.
|
||||
- Project instructions require Gitea coordination, ownership preservation and
|
||||
durable handoffs. Current root reserves one Cargo/native operator per host.
|
||||
Do not infer restart, usage reset or credential disclosure authorization.
|
||||
Deliver a complete, usable OA/SA release on Windows and Linux, with one explicit
|
||||
reST semantic contract and equivalent graphical, textual and REST access. Include
|
||||
constraints/calculations, quantities/units, maintained libraries, behavior/state,
|
||||
traceability and navigable offline help. Reduce cognitive load and visual clutter;
|
||||
small and large models must be practical using text alone. Later Arcadia layers
|
||||
remain future scope. Compilation or a pleasant happy path is not completion.
|
||||
|
||||
## Verified facts
|
||||
|
||||
- The independent scenario checker compiled with warnings denied and passed its
|
||||
self-check, deterministic fixture generation and complete baseline check on this
|
||||
host. Its eight OA/SA checkpoints and exact UUID/source restoration comparisons
|
||||
are evaluator evidence, not native Studio acceptance. Exact inputs/hashes are in
|
||||
[the fixture instructions](fixtures/scenario-authoring/README.md).
|
||||
- Local start was cleanff615d0. Root decoded/hash-verified/imported published3978,
|
||||
c6 and4bb bundles; merged c6 as c81e285 and is integrating creation4bb. There were
|
||||
no production cherry-pick conflicts; docs/attributes require evidence union.
|
||||
The current goal is copied from the user's latest file.
|
||||
- Read-only integration comparison finds equivalent workspace/Sensor code in c6;
|
||||
replaying3978 or d114 is unnecessary. Core source is unchanged betweenff andc6.
|
||||
B4 is still a test-only projection. [Audit](release-integration-ytr83r-20260911.md).
|
||||
- Imported source implements named behavior creation, exact prepared-batch
|
||||
correlation, success-only selection, raw-draft guards, recoverable original
|
||||
layer and modal-priority Escape. These are source facts; combined local runtime
|
||||
acceptance is pending.
|
||||
- Earlier-host desktop642 and653 suites, scoped native scenarios/creation,
|
||||
packaging25 notices and source experiments retain exact attribution in
|
||||
[STATE.md](STATE.md). They are not new local passes.
|
||||
- The original transferred creation oracle incorrectly equates physical disk files
|
||||
with reachable sources during Undo. Later external v2 corrects the evaluator
|
||||
with explicit origin/retained-byte rules; exact v2 is not yet in this transfer.
|
||||
- The separate baseline-context experiment passed218 assertions; explicit
|
||||
one-level overrides reduce repeated stable assumptions while complete frozen
|
||||
definition environments remain necessary. Proposed syntax is not source7.
|
||||
|
||||
- Current local implementation is `80cf197` on `codex/behavior-authoring-20260910`, following
|
||||
baseline `1797516`. Local commits cover B1/B2/B3 authoring, nullable history cache
|
||||
(`b6b76ef`), external palette integration (`aed40d7`), cfg(test) lifecycle projection
|
||||
(`eb5161b`), history seed correction (`4ecad78`) and exact-identity native oracle.
|
||||
Later imports add focus recovery, exact packaging notices and scenario workspace/
|
||||
owner restoration. Root80cf197 fixes document/scenario viewport Sensor identity
|
||||
with a real mounted red-before/green-after regression.
|
||||
- This fresh host has task-local Rust/Cargo 1.98.1 GNU/LLVM and verified LLVM-MinGW.
|
||||
The integrated full desktop suite passes642/642, zero failed/ignored, with a
|
||||
warning-free build. History and pure lifecycle tests are included. Current GUI
|
||||
build/native and strict lint remain open. [Exact hashes/logs](STATE.md).
|
||||
- Strict language HTML regeneration and the source7 OpenAPI checker passed locally:
|
||||
72 fixtures, 204 schemas and 90 scalar leaves. Actual isolated Capella scenario,
|
||||
activity/lifeline and LOOP creation was saved/inspected; this is reference study,
|
||||
not Studio acceptance. [Native benchmark](release-capella-scenario-benchmark-20260910.md).
|
||||
- Core/source7 already implements substantial direct behavior, typed data/ports,
|
||||
contextual chain links, maintained message-operation identity, semantic reviews,
|
||||
artifacts, hosted source envelopes and recovery. Historical absence claims must
|
||||
be checked against code and newer scoped evidence, not copied forward.
|
||||
- [Requirements audit](release-requirements-delta-20260910.md): Constraint and other
|
||||
expression strings are descriptive, with no calculation/binding/result evaluator;
|
||||
unit strings persist/inherit without dimensional compatibility or conversion;
|
||||
named types/sequence/scenario reuse and includes exist, but there is no maintained
|
||||
cross-project package/version/instance/update contract. These are explicit gaps.
|
||||
- The same audit identifies concrete unbounded Constraint target choices and generic
|
||||
expanded collection editors. Explorer already has hierarchy/search/paging; the
|
||||
problem is targeted, not a claim that all selection is flat.
|
||||
- Gitea #79's same-selected-ID/visible-owner defect is fixed in the imported
|
||||
scenario checkpoint; owner restoration and pending-draft guards pass current
|
||||
tests. B4 independent review #114 adds Scene integration requirements for actual
|
||||
lifetime extents, branch-local activation clipping, incomplete lanes and self arrows.
|
||||
- Codex-9e8r6t is a separate host with independent Cargo/native leases. It owns
|
||||
scenario workspace/B3/local behavior creation, palette and platform/packaging;
|
||||
coherent workspace/package integration is imported, while newer named behavior
|
||||
creation and docs changes await transfer. Both hosts report direct push auth
|
||||
unavailable. MCP/anonymous fetch and verified bundle exchange remain usable.
|
||||
- Current Linux acceptance is open; this host has no installed WSL distribution.
|
||||
Historical Linux core/server/cross-build results have exact older snapshot scope.
|
||||
The earlier denied guest workaround did not run and must not be bypassed.
|
||||
## Assumptions and unresolved questions
|
||||
|
||||
## Assumptions
|
||||
- Combining already coherent desktop slices should preserve behavior; fresh build,
|
||||
automated and native gates must test that assumption.
|
||||
- The baseline/library designs can fit existing atomic Project/Command/source
|
||||
boundaries; exact references, deletion, transition, imports, freezing and
|
||||
numeric rules still need ratified contracts and falsification.
|
||||
- Pinned package provenance must be distinguished from checked type compatibility;
|
||||
unchanged quantity kinds cannot become incompatible merely through cosmetic
|
||||
repackaging without a deliberate policy. Energy and Torque remain distinct.
|
||||
- Which supported environment will complete current Linux GUI/service/package
|
||||
execution remains a release question. Old failed or denied experiments do not
|
||||
establish a current successful environment.
|
||||
- Large-model human/AI task usability, cross-file refactoring, actual chooser
|
||||
latency/keyboard/minimum geometry and complete native lifecycle behavior remain
|
||||
to be measured. Parser admission or a widget experiment is insufficient.
|
||||
|
||||
- Compact contextual tools and an adequately sized scenario workspace can reduce
|
||||
friction; only actual engineering tasks at minimum/wide sizes can validate this.
|
||||
- A bounded pure analysis model and pinned reusable packages may satisfy the new
|
||||
requirements without full language/runtime adoption. This is a candidate, not a
|
||||
selected architecture or a permission to treat metadata as semantics.
|
||||
- Existing shared core/source/history boundaries remain suitable for additions;
|
||||
foundational examples and independent criticism must test that assumption.
|
||||
## Candidate designs and selected directions
|
||||
|
||||
## Open questions
|
||||
The imported [analysis proposal](release-analysis-semantics-design-20260910.md),
|
||||
[library proposal](release-libraries-semantics-design-20260910.md),
|
||||
[paired critique](release-semantic-proposals-review-20260910.md) and
|
||||
[textual authoring design](release-textual-authoring-design-20260911.md) retain
|
||||
alternatives and counterexamples. Metadata-only analysis and bare source includes
|
||||
do not meet evaluated quantities or maintained libraries.
|
||||
|
||||
- What precise owned-value, calculation, constraint-result, quantity-kind, unit and
|
||||
numerical contracts meet mass/power/latency and affine/dimensional edge cases?
|
||||
- Which library definition/instance/pinning/binding/update design preserves stable
|
||||
identities, local engineering edits and offline reproducibility across projects?
|
||||
- What migration and OA↔SA treatment follows from those contracts without guessing
|
||||
executable meaning from old strings or silently changing old models?
|
||||
- How can text-only creation establish library instance bases/maps, preserve
|
||||
compatibility across cosmetic package revisions, export subjectless cases, and
|
||||
transition mounted OA/SA data without hidden GUI normalization or silent forks?
|
||||
- Do explicit baseline values with one-level case overrides or complete per-case
|
||||
bindings better support repeated study maintenance and reproducible evaluation?
|
||||
- Which source-preserving refactoring/navigation and grammar changes reduce actual
|
||||
engineering effort while retaining stable identity and cross-file ownership?
|
||||
- Do current real gestures, exact caller return, nested scopes and lifecycle markers
|
||||
remain usable and correct under minimum sizing, scrolling, zoom and dirty drafts?
|
||||
- Which uncovered teaching, traceability, transition, saved-view, state/data, hosted
|
||||
and platform cases remain after current-binary acceptance? What supported Linux
|
||||
environment can complete the remaining actual runtime gate?
|
||||
- Does "standardized" require any external conformance beyond the project's precise
|
||||
interoperable spec/API? Full OMG conformance is not inferred merely from comparison
|
||||
to SysML v2; explicit claims require a mapped and verified contract.
|
||||
Codex-956atf root selected property-owned baseline values/formulas with explicit
|
||||
ModelBaseline/Case evaluation and one-level case overrides for contract refinement.
|
||||
No hidden default case or UI-dependent evaluation; inherited formulas use the
|
||||
effective requested case, and complete freeze captures definitions/provenance.
|
||||
Exact numeric, library normalization/type compatibility and transition details
|
||||
remain open. This direction is recorded in [DECISIONS.md](DECISIONS.md), not silently
|
||||
treated as completed production semantics.
|
||||
|
||||
## Candidate hypotheses / designs
|
||||
The external staged prerequisite design reserves source/consumer identities,
|
||||
keeps the parent context/rawtext/slot, stages locally and creates source+consumer
|
||||
in one atomic final command. It must not implicitly allocate work, involve
|
||||
capabilities, retarget an Exchange-fixed endpoint or accept a different editor.
|
||||
Qualified Action allocation remains a distinct engineering choice.
|
||||
|
||||
The [requirements delta](release-requirements-delta-20260910.md) compares metadata/
|
||||
snippets, bounded pure engineering analysis with maintained pinned libraries,
|
||||
external evaluators, and full standards adoption. Metadata alone fails the explicit
|
||||
new semantics; external tools alone still need binding/result contracts. The report
|
||||
recommends the bounded route for root synthesis, not as a ratified decision.
|
||||
## Retained implementation decisions
|
||||
|
||||
Independent maximum-reasoning tracks now compare owned engineering properties
|
||||
versus analysis contexts; calculation definitions/applications; numeric/unit rules;
|
||||
and copy, linked-definition, live-instance or pinned-definition/editable-instance
|
||||
library architectures. Require concrete falsifiers, source/API migration effects,
|
||||
identity/history/recovery behavior and independent critique before convergence.
|
||||
The completed analysis/library proposals and paired review remain unratified.
|
||||
An isolated executable text-only fixture admits without warnings and passes exact
|
||||
source/identity/rename/reparent/file-move/default checks. Separate baseline-versus-
|
||||
complete-case and anchored chooser experiments are active, with no production
|
||||
metamodel or selector integration implied.
|
||||
|
||||
The subsequent context experiment passed218 assertions: shared property baselines
|
||||
and one-level overrides reduce repeated input maintenance while retaining explicit
|
||||
independent freeze. Root selected that B direction for precise contract refinement;
|
||||
quantity/library/source details remain open. [Decision](DECISIONS.md),
|
||||
[experiment and limits](release-analysis-context-experiment-20260911.md).
|
||||
|
||||
## Decisions retained
|
||||
|
||||
- Keep three Rust crates and one authoritative typed Project with validated atomic
|
||||
Commands. Separate semantic identity/ownership, allocation/reference/order and
|
||||
diagram geometry. Forms are closed adapters, not a second metamodel. New persistent
|
||||
semantics require core/source/UI/API/reference/transition parity. [Decisions](DECISIONS.md).
|
||||
- Preserve authored source ownership/comments/includes, exact identity and accepted
|
||||
model/source history. Source writeback must succeed before adoption. Raw invalid,
|
||||
excluded or rejected drafts survive; navigation/tools must not implicitly accept
|
||||
another editor. Recovery validates/replans rather than trusting serialized commands.
|
||||
- Keep one authoritative typed Project, validated atomic Commands, stable
|
||||
identities and explicit references. Semantic ownership/allocation/order and
|
||||
diagram geometry remain distinct; forms are adapters, not a second metamodel.
|
||||
- Preserve source ownership/comments/includes and exact model/source history.
|
||||
Writeback succeeds before adoption. Invalid/rejected raw drafts survive and
|
||||
browsing/tool selection does not silently accept another editor. Recovery
|
||||
validates/replans rather than trusting serialized commands.
|
||||
- Semantic reconciliation uses finite typed facets, frozen baselines, explicit
|
||||
mappings, actual destination slots and a single atomic candidate. Do not infer
|
||||
identity by name or apply reviewed rows as sequential independent edits.
|
||||
[Foundation](release-semantic-batch-foundation-design.md),
|
||||
[artifact contract](release-semantic-artifacts.md).
|
||||
- Layer transitions are explicit engineering decisions, not automatic propagation.
|
||||
Behavior-root navigation must establish the requested owner while preserving
|
||||
unrelated architecture presentation. Ports/allocation and contextual occurrences
|
||||
retain their distinct domain meaning. [Source7 contract](release-source7-integration-decision-20260906.md).
|
||||
- Hosted revision/source envelopes and ETag checks remain atomic; credentials stay
|
||||
out of persisted models and repository. Linux journal publication retains the
|
||||
selected no-replace invariant, with measured limits, not an overwrite fallback.
|
||||
[Journal decision](release-linux-journal-publication.md).
|
||||
- Repair/evaluate the compact palette informed by native Capella evidence; do not
|
||||
return to the rejected horizontal toolbar. Lifecycle projection remains isolated
|
||||
under cfg(test) until coordinated Scene integration and actual acceptance.
|
||||
- Preserve historical scope decisions as history. In particular, architecture-only
|
||||
SVG is implemented and behavior SVG was deferred; that is not proof of satisfying
|
||||
the revised release objective. Reassess older exclusions against current scope.
|
||||
mappings and one atomic candidate. Names alone never establish identity.
|
||||
- OA↔SA transitions are explicit engineering decisions. New persistent semantics
|
||||
need validation/reference/deletion/transition/source/API/UI/history parity.
|
||||
- Exact evidence bytes and host attribution survive integration. No focused
|
||||
test total is added to a full-suite count; old binary acceptance does not
|
||||
transfer to newly merged code.
|
||||
|
||||
## Current strategy
|
||||
## Current strategy and coordination
|
||||
|
||||
Finish the GUI/native loop after the green full desktop suite while separate
|
||||
agents investigate uncertain foundations. Integrate only coherent, verified
|
||||
external checkpoints respecting ownership. Use independently constructed complete
|
||||
model/source oracles and exact snapshot comparison for identity/history. Ratify
|
||||
analysis/library contracts through alternatives and falsifying examples, then
|
||||
implement shared semantics and ergonomic authoring together. Close current
|
||||
cross-platform/service/package and independent end-state gates before handoff.
|
||||
Root owns local integration, serialized builds, native inputs and final synthesis.
|
||||
The local audit resolves evidence and reviews source; independent server review
|
||||
has its own report. Codex-9e8r6t owns staged sources/first actions and source CLI;
|
||||
Codex-956atf owns chooser and semantic contracts. Read Gitea issue #1/Wiki before
|
||||
resuming, obtain exact coherent transfer heads, and respect their source ownership.
|
||||
|
||||
The [archived Task Ledger](history/2026-09-10-ledgers-before-continuation-refresh/TASK_LEDGER.md)
|
||||
and [archived STATE](history/2026-09-10-ledgers-before-continuation-refresh/STATE.md)
|
||||
preserve all older claims, decisions and evidence links exactly. Relative report
|
||||
links inside those byte-preserved files resolve from their original `harness/`
|
||||
context. Their historical test totals and process holds are not live status.
|
||||
First finish and verify the integrated current source. Obtain corrected evaluator
|
||||
and later evidence. Then close real remaining lifetime, modeling/textual,
|
||||
analysis/library and platform gates with independent criticism and whole-task
|
||||
acceptance. Update facts, assumptions and decisions as evidence changes them.
|
||||
|
||||
Reference in New Issue
Block a user