Step 9: ruthlessly simplify only actor-session performance/resource optimizations in src/typed_ooda/ledger.rs and src/typed_ooda/schema.rs. Preserve all stated security, validation, provenance migrati

[rysweet]

Task Description

Step 9: ruthlessly simplify only actor-session performance/resource optimizations in src/typed_ooda/ledger.rs and src/typed_ooda/schema.rs. Preserve all stated security, validation, provenance migration, transaction, constructor, interface, telemetry, error, and observable-behavior invariants. Retain only demonstrably safe optimizations; do not cache. Run exactly cargo test --quiet --test typed_ooda_actor_session_scope --test typed_ooda_goal_session_workflow --test typed_ooda_security_regressions with env -u SIMARD_OBSERVE_ONLY and NODE_OPTIONS=--max-old-space-size=32768. Make no docs, dependency, unrelated, test expansion, or commit changes.

Requirements

Final Requirements

No material ambiguity remains.

1. Modify only actor-session optimization paths in:
   • src/typed_ooda/ledger.rs
   • src/typed_ooda/schema.rs
2. Simplify or remove optimization-specific complexity unless behavioral equivalence is demonstrable.
3. Retain authoritative database reads and provenance verification; add or retain no caching in affected paths.
4. Preserve all security, validation, migration atomicity, transaction, constructor, interface, telemetry, error, canonicalization, and observable-behavior contracts.
5. Preserve constant-time digest checks, canonical evidence bytes/order, replay and expiry semantics, and fail-closed behavior.
6. Do not change tests, documentation, manifests, lockfiles, dependencies, unrelated code, or commits.
7. Run exactly once:

env -u SIMARD_OBSERVE_ONLY NODE_OPTIONS=--max-old-space-size=32768 cargo test --quiet --test typed_ooda_actor_session_scope --test typed_ooda_goal_session_workflow --test typed_ooda_security_regressions

Decision: Optimization candidates are not mandatory. If equivalence cannot be established directly from semantics and the required tests, remove or leave the optimization unchanged rather than speculating. Requirements are ready for design.

Acceptance Criteria

• All explicit requirements met
• Tests passing
• Philosophy compliant
• Documentation updated

Classification

Generated via default-workflow recipe