create-context

Create Context

Turn the raw documents in the in-folder into a prioritised, token-budgeted snapshot that later sessions load in one read.

Layout

.context/session/in/                      immutable input: users drop documents here, no command edits it
.context/session/ctx/                     generated snapshot: manifest, copies, summaries
.context/session/CONTEXT-baseline-llm.md  single load point, 2000 tokens at most

Mindset

• Use the in-folder as the source of truth. The manifest mirrors it faithfully.
• Keep the snapshot scoped to the session's open questions. Include only what shapes decisions.
• Keep one manifest per session. Two manifests in one folder leave load-context unable to choose.
• State the origin of every constraint, assumption and decision that enters the baseline.

When to Use

• Use it once per project when raw documents sit in the in-folder and no ctx snapshot exists.
• Use it with --force after the source documents changed materially.
• Use it when load-context reports a missing manifest.

When Not to Use

• Do not use it when the ctx snapshot is current. A rerun without --force stops, and --force discards existing summaries.
• Do not use it when the in-folder is empty. There is nothing to scan.
• Do not use it to refresh one document. Update that summary and its manifest entry by hand.
• Use save-context instead to store live session state in a named stream.

Steps

1. Guard the prerequisites. Stop on a missing in-folder, and stop on an existing ctx folder unless --force was passed.

[ -d .context/session/in ] || { echo "No in-folder found. Add source files first." >&2; exit 1; }
[ -d .context/session/ctx ] && [ "$ARGUMENTS" != "--force" ] && { echo "ctx exists. Use --force." >&2; exit 1; }

1. Scan the in-folder with the bundled script. It lists md, txt, csv, yaml, yml and json files with a token estimate, and skips sensitive paths.

./scripts/scan-in-folder.sh .context/session/in