[1.0 T2] Add stable record references and explicit decision lifecycle #178

Problem and outcome

Implement only the identity and replacement support justified by T1, without turning decision status into an approval workflow.

Interaction contract

Keep FluencyLoop. Proposed positioning: Stay fluent as people and agents evolve the product.

Use retained product reasoning automatically. Explain consequential choices at the right depth. Recommend a path. Continue within agreed intent. Ask when human judgment is needed. Update the shared model at natural boundaries.

The flagship goal/principles/precedents/tradeoffs reasoning is integrated into the existing design explanation at proportional depth. It is not a mandatory recital, proposal form, or new approval exchange. People must remain able to understand and challenge the design.

Scope

• Use the T1 report to narrow the schema; retain or defer fields based on observed failures. Define durable references, applicability, and replacements while preserving legacy records.
• Separate delegated agent choices, explicitly confirmed human choices, implementation state, and evidence trust. A delegated choice can be active without a separate human-approval event.
• Resolve missing refs, cycles, and concurrent successors consistently across both core runtimes and the site. Expose ambiguity without selecting authority from file order.
• Keep historical metadata gaps advisory. Ask only if an underlying ambiguity materially affects the requested work. Support repository design artifacts without claiming they are deployed code.

Acceptance criteria

• T1 evidence is linked and unnecessary lifecycle machinery is removed or deferred.
• Renaming or replacing a decision preserves references and provenance.
• Delegated agent decisions can be used without requesting human confirmation solely for metadata.
• Legacy approval is never inferred; missing metadata alone cannot block normal implementation.
• Bash, PowerShell, and site readers agree on effective records and unresolved conflicts.

Validation

Use Bats/Pester and shared reader fixtures for legacy identities, replacement, independent authority/trust states, cycles, and conflicts. Include the case of incomplete historical metadata with otherwise sufficient task intent; run core checks without Node.

Starting points

plugins/fluencyloop/scripts/{bash,powershell}/common., add-decision., check.*; plugins/fluencyloop/site/server.js identityFor/readStore; tests/store-schema.bats and tests/powershell/store-schema.Tests.ps1

Constraints

• Target dev; main distributes releases. No runtime implementation occurs in the planning PR.
• T1 is an observed pilot using existing artifacts before new infrastructure. Use its evidence to retain, narrow, or defer later scope.
• Recommend and continue within authorized intent; ask with a recommendation only for consequential unresolved judgment. Batch independent questions, reuse settled answers, and wait for dependent work. Silence is not approval.
• Absent briefs, historical link gaps, stale prose, and unreviewed metadata alone are advisory. Do not require onboarding, cleanup, or retrospective approvals to work.
• Unknown familiarity is not fluency and does not automatically require a blocking probe/check. Support requested guided learning without quizzes; keep calibration/preferences private. T5 explicitly updates inherited pause rules.
• Capture rationale once, link mechanical views, record outcome deviations at natural closure, distill once at wrap-up, and reuse unchanged context.
• Preserve append-only history/provenance; Bash and PowerShell implement the same contract. Core remains Node-optional; no new database, hosted service, or vector search.

Dependencies and size

• Task: T2
• Relative size: L (not a calendar estimate)
• Depends on: T1: [1.0 T1] Pilot recommendation-first design and define the flow contract #177
• Milestone: https://github.com/baokhang83/fluencyloop/milestone/3
• Plan: draft source
• Planning PR: docs: propose FluencyLoop 1.0 shared product direction and design #189