Implement DBE feedback: refs, drift, guardrails #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/decision-refs-and-drift-policy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Apply a round of DBE-plugin feedback: make decision references explicit and
archive-first, switch decision ids to per-archive prefixes, make
documentation drift always-fixed, add an engineering stance, harden the git
and external-write guardrails, and ship a global CLAUDE.md installer.
Decision references:
(ARCH/DSGN/TECH/CODE/AGNT/COMM-NNNN); schema.json pattern, the
decision-engine SKILL, and worked examples updated
archive-entry-first; seam notes in plan-lifecycle, project-structure, and
agent-guidance
Drift policy:
as a TODO; the stale-terms table is limited to already-fixed renames; the
audit commands disposition drift as fixes. This bumps the AGENTS template
marker dbe-agents-template v1 to v2 (managed content)
Engineering stance:
fit, tests first, review the whole change) in guidance.md and both AGENTS
mirrors
Guardrails:
writes; guard-history-rewrite now gates any git push; operating-standards
carries the never-write-to-an-external-service rule
CLAUDE.md installer:
New Files:
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com