Skip to content

feat!: include behavior context by default - #3

Merged
Donmclean merged 1 commit into
mainfrom
codex/default-behavior-context
Oct 7, 2026
Merged

Donmclean merged 1 commit into
mainfrom
codex/default-behavior-context

Conversation

@Donmclean

Copy link
Copy Markdown
Member

Agents need a clear explanation of domain rules and expected outcomes before changing business logic. New scaffolds now include context/behavior.md as a default-selected add-on alongside glossary, with INDEX routing and readiness metadata. The template covers concepts, workflows, decisions, transitions, exceptions, and the distinction between implemented behavior and intended changes. Deeper topics live in project-owned documents under context/behavior/.

Architecture guidance now focuses on components, implementation flows, and technical invariants. Existing scaffolds preserve their configured add-ons during update and fresh-clone hydration. After upgrading ctx, adopt behavior explicitly with:

ctx update
ctx add behavior

Use ctx init --without behavior to omit behavior, or --without behavior,glossary for the fixed core only. Managed guidance advances to template revision 2.0.1; layout and schema remain at version 2. Frozen legacy templates are unchanged.

Validation passed:

  • Full Go race suite and vet.
  • Lifecycle smoke test covering default behavior creation and routing.
  • Integration tests covering adoption in team/local modes, preservation of project-owned content, older-scaffold hydration, and freshness checks for parent/child behavior documents.
  • Documentation links, project-fact template metadata, release-script syntax, and npm package dry run.
  • Whitespace checks and comparison of frozen legacy templates against main.

Add an evidence-tracked behavior document for business/domain rules,
decisions, state transitions, and expected outcomes. Route deeper topics
through project-owned children under context/behavior/ and clarify the
boundary with architecture.

Advance managed template guidance to revision 2.0.1. Preserve configured
add-ons during update and hydration, and support explicit adoption with
ctx update followed by ctx add behavior.

BREAKING CHANGE: New layout-v2 scaffolds select behavior and glossary by default.
Use --without behavior,glossary, or an explicit empty InitOptions.Addons slice,
for the fixed core only. Existing scaffolds retain their selected add-ons;
after upgrading ctx, run ctx update followed by ctx add behavior to adopt
the new document.
@Donmclean
Donmclean merged commit 5c3b88e into main Oct 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant