Skip to content

Add v0.1 spec, execution plan, and project scaffold - #1

Merged
tylerhogarth merged 6 commits into
mainfrom
feat/project-scaffold
Sep 1, 2026
Merged

Add v0.1 spec, execution plan, and project scaffold#1
tylerhogarth merged 6 commits into
mainfrom
feat/project-scaffold

Conversation

@tylerhogarth

Copy link
Copy Markdown
Owner

Establishes the tod v0.1 project: a settled spec and execution plan, plus the repository foundation the plan's first milestone calls for. tod is an operator harness that guides AGENTS.md-compatible coding agents for non-technical builders; it never scaffolds application code and never deploys.

Changes

  • Spec and plan (project/tod-v0.1/): the outline is replaced with a full spec (requirements, non-goals, acceptance criteria) and a five-milestone execution plan with test cases mapped to every acceptance criterion. Key design points: config/state harness (no launcher), marker-block ownership inside possibly pre-existing shared files, agent-led onboarding, and deterministic CLI mutations.
  • Scaffold: Bun + TypeScript + Biome + bun test, with better-result and zod as the only runtime dependencies. CI runs typecheck, lint, and tests on PRs. Package is tod-ai, exposing a tod binary.
  • CLI skeleton (src/run.ts, src/commands/): routing plus stubs for init, new, sync, status. Help text and errors target coding agents: when-to-use guidance and a what/why/fix error format with stable exit codes (src/output.ts).
  • Write boundary (src/boundary.ts): symlink-resolved containment check against an allowlist of user-level roots plus operator-designated project directories. All future filesystem writes route through it.
  • Repo instructions (AGENTS.md, CLAUDE.md symlink): engineering rules for agents working on tod: operator-system safety, non-destructive marker-block edits, determinism-first tooling, dependency policy.

Why

tod runs on the machines of non-technical operators, so safety primitives come first: the boundary module and the non-destructive editing rules exist before any command can write to disk. The CLI is agent-facing rather than human-facing, which shapes help text and error output as machine-actionable guidance. Marker blocks (rather than whole-file ownership) let tod coexist with an operator's existing AGENTS.md instead of overwriting it.

🤖 Generated with Claude Code

tylerhogarth and others added 6 commits September 1, 2026 08:24
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Help text and errors target coding agents: when-to-use guidance and a
what/why/fix error format with stable exit codes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
All future writes route through an explicit allowlist of user-level
roots plus operator-designated project directories.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@tylerhogarth
tylerhogarth merged commit a356208 into main Sep 1, 2026
1 check passed
@tylerhogarth
tylerhogarth deleted the feat/project-scaffold branch September 1, 2026 10:08
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