stratarc 0.1.0__tar.gz

stratarc-0.1.0/.gitignore

@@ -0,0 +1,57 @@
+# python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# virtual environments
+.venv/
+venv/
+env/
+
+# build outputs
+build/
+dist/
+site/
+*.whl
+
+# secrets
+.env
+.env.*
+!.env.example
+settings.local.json
+
+# os
+.DS_Store
+
+# internal work product: prompts, questions, provenance, session notes and
+# any snapshot a hook writes; never published
+.docs/
+
+# editor state
+.obsidian/
+.obsidian-stage-*/
+
+# agent instruction files and runtime directories at the repository root:
+# generated per machine by the operator's own configuration engine, never
+# tracked here; the bundled template and the examples keep their own copies
+/AGENTS.md
+/CLAUDE.md
+/CODEX.md
+/GEMINI.md
+/OPENCODE.md
+/.claude/
+/.codex/
+/.gemini/
+/.cursor/
+/.opencode/
+/.agents/
+/llm-root-control-plane.md
+/.llm-root-deploy.json
+/.github/attribution-check/
+/.github/workflows/attribution-check-comment.yml

stratarc-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Kevin Lappe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

stratarc-0.1.0/PKG-INFO

@@ -0,0 +1,69 @@
+Metadata-Version: 2.5
+Name: stratarc
+Version: 0.1.0
+Summary: One agent configuration source, rendered into every agent runtime.
+Project-URL: Repository, https://github.com/klappe-pm/stratarc
+Author: Kevin Lappe
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.11
+Provides-Extra: test
+Requires-Dist: jsonschema; extra == 'test'
+Requires-Dist: pytest; extra == 'test'
+Provides-Extra: ui
+Requires-Dist: textual>=8.2.0; extra == 'ui'
+Description-Content-Type: text/markdown
+
+# stratarc
+
+stratarc compiles one configuration source root (instructions, rules, hooks, skills, commands, agents and permissions) into the native configuration of each agent runtime you use, then deploys it to that runtime's directory. You edit one tree; stratarc writes five formats. It ships as a Python package with shell hooks and needs only the Python 3.11 standard library at runtime.
+
+Compatibility targets: Claude Code, Codex, Gemini CLI, Cursor and OpenCode.
+
+## status
+
+The engine was extracted from a private repository. The first release is `v0.1.0`, published as a GitHub release; there is no PyPI package yet, so you install from the tagged repository. `init`, `sync`, `check`, `diff`, `prune`, `reconcile`, `validate`, `doctor` and the `config`, `provider`, `adapter`, `log`, `verify`, `source`, `project`, `runtime`, `agent` and `account` resources are implemented, as is the optional terminal interface `stratarc ui`. The [cli backlog](developer-docs/explanation/cli-backlog.md) lists what ships and what is next, and [changelog.md](changelog.md) records changes.
+
+## quickstart
+
+Install the command. Until the package reaches PyPI, install the tagged release from the repository.
+
+```bash
+pipx install git+https://github.com/klappe-pm/stratarc@v0.1.0
+```
+
+Once it is on PyPI:
+
+```bash
+pipx install stratarc
+```
+
+Scaffold a source root:
+
+```bash
+stratarc init ~/stratarc-source
+```
+
+Edit `~/stratarc-source/stratarc.toml` to name the runtimes you use, then edit the rules, skills and hooks under the same directory.
+
+Preview what a deployment would change without writing anything, then deploy to every enabled runtime:
+
+```bash
+cd ~/stratarc-source && stratarc diff
+cd ~/stratarc-source && stratarc sync
+```
+
+## documentation
+
+Two trees, one per audience, each arranged by [Diátaxis](https://diataxis.fr/) quadrant: tutorials, how-to guides, reference and explanation.
+
+- I use stratarc, where do I start: [getting started](docs/tutorials/getting-started.md), then the rest of [docs](docs/README.md).
+- I change stratarc, where do I start: [first contribution](developer-docs/tutorials/first-contribution.md), then the rest of [developer-docs](developer-docs/README.md).
+
+## support-and-contributing
+
+[support.md](support.md) says where to ask for help and where to file an issue. [contributing.md](contributing.md) holds the contribution guidelines. Report vulnerabilities privately as described in [security.md](security.md).
+
+## license
+
+MIT. See [LICENSE](LICENSE).

stratarc-0.1.0/README.md

@@ -0,0 +1,53 @@
+# stratarc
+
+stratarc compiles one configuration source root (instructions, rules, hooks, skills, commands, agents and permissions) into the native configuration of each agent runtime you use, then deploys it to that runtime's directory. You edit one tree; stratarc writes five formats. It ships as a Python package with shell hooks and needs only the Python 3.11 standard library at runtime.
+
+Compatibility targets: Claude Code, Codex, Gemini CLI, Cursor and OpenCode.
+
+## status
+
+The engine was extracted from a private repository. The first release is `v0.1.0`, published as a GitHub release; there is no PyPI package yet, so you install from the tagged repository. `init`, `sync`, `check`, `diff`, `prune`, `reconcile`, `validate`, `doctor` and the `config`, `provider`, `adapter`, `log`, `verify`, `source`, `project`, `runtime`, `agent` and `account` resources are implemented, as is the optional terminal interface `stratarc ui`. The [cli backlog](developer-docs/explanation/cli-backlog.md) lists what ships and what is next, and [changelog.md](changelog.md) records changes.
+
+## quickstart
+
+Install the command. Until the package reaches PyPI, install the tagged release from the repository.
+
+```bash
+pipx install git+https://github.com/klappe-pm/stratarc@v0.1.0
+```
+
+Once it is on PyPI:
+
+```bash
+pipx install stratarc
+```
+
+Scaffold a source root:
+
+```bash
+stratarc init ~/stratarc-source
+```
+
+Edit `~/stratarc-source/stratarc.toml` to name the runtimes you use, then edit the rules, skills and hooks under the same directory.
+
+Preview what a deployment would change without writing anything, then deploy to every enabled runtime:
+
+```bash
+cd ~/stratarc-source && stratarc diff
+cd ~/stratarc-source && stratarc sync
+```
+
+## documentation
+
+Two trees, one per audience, each arranged by [Diátaxis](https://diataxis.fr/) quadrant: tutorials, how-to guides, reference and explanation.
+
+- I use stratarc, where do I start: [getting started](docs/tutorials/getting-started.md), then the rest of [docs](docs/README.md).
+- I change stratarc, where do I start: [first contribution](developer-docs/tutorials/first-contribution.md), then the rest of [developer-docs](developer-docs/README.md).
+
+## support-and-contributing
+
+[support.md](support.md) says where to ask for help and where to file an issue. [contributing.md](contributing.md) holds the contribution guidelines. Report vulnerabilities privately as described in [security.md](security.md).
+
+## license
+
+MIT. See [LICENSE](LICENSE).

stratarc-0.1.0/developer-docs/README.md

@@ -0,0 +1,19 @@
+# developer-docs
+
+Documentation for people who change stratarc: you clone the repository, run its tests, add an adapter or fix a bug, and open a pull request. It uses the same four [Diátaxis](https://diataxis.fr/) quadrants as the user documentation under [docs](../docs/README.md), so the folder a page sits in tells you what kind of page it is. Nothing here is needed to use stratarc; everything here assumes you have read the user documentation for the part you are changing.
+
+## tutorials
+
+Lessons that take you through a task from start to finish, for someone new to the codebase. Start with [first contribution](tutorials/first-contribution.md), which goes from a fresh clone to a passing test suite and a pull request. Index: [tutorials](tutorials/README.md).
+
+## how-to-guides
+
+Recipes for a specific development goal. [add a runtime](how-to-guides/add-a-runtime.md) covers writing an adapter for another agent runtime, [run the tests](how-to-guides/run-the-tests.md) covers the suite, its markers and the CI checks, and [cut a release](how-to-guides/cut-a-release.md) covers versioning, the changelog and tagging. Index: [how-to guides](how-to-guides/README.md).
+
+## reference
+
+Lookup pages that describe the codebase as it is. [source layout](reference/source-layout.md) describes the source root that `stratarc init` creates and which runtimes consume each part, and [package data](reference/package-data.md) describes how the assets under `stratarc/data/` are packaged and resolved through `importlib.resources`. Index: [reference](reference/README.md).
+
+## explanation
+
+Discussion of why stratarc is built the way it is. [architecture](explanation/architecture.md) explains how one source root becomes several runtime configurations, and [decisions](explanation/decisions/README.md) holds stratarc's own decision records, one per choice that shaped the code. Index: [explanation](explanation/README.md).

stratarc-0.1.0/developer-docs/explanation/README.md

@@ -0,0 +1,8 @@
+# explanation
+
+Explanation pages give the reasoning behind the code: how the pipeline is shaped and why, what was decided and what was rejected. They are for a contributor who wants to understand stratarc before changing it, and they are the right place to read when a change you are planning touches something a decision record already settles.
+
+## pages
+
+- [architecture](architecture.md): how one source root becomes a configuration for each runtime, stage by stage.
+- [decisions](decisions/README.md): stratarc's own decision records, one per choice that shaped the code.

stratarc-0.1.0/developer-docs/explanation/decisions/README.md

@@ -0,0 +1,75 @@
+# decisions
+
+This folder holds stratarc's decision records: one page per choice that shaped the code, written when the choice was made, so a later contributor can see what was decided, what was considered instead and why. A record is never rewritten once accepted; a reversal is a new record that names the one it supersedes. Read the records that touch a part of the code before proposing to change it.
+
+## format
+
+Each record is a file named `YYYY-MM-DD-<short-kebab-title>.md` with these sections: `## context` (the situation and the forces at play), `## decision` (what was chosen, in one paragraph), `## alternatives` (what else was considered and why it lost), and `## consequences` (what follows, good and bad). Add the record to the list below when it is accepted.
+
+## records
+
+Every record below is dated 2026-10-09 and was backfilled in one pass after the choices were made, so each carries the alternatives that were weighed then. The alternatives written from the code and the brief rather than from the maintainer's own words are marked for review in their pages. The terminal interface library record was proposed and open; the Textual record supersedes it, and the record stays as written. The two open points in accepted records, the `_modes` syntax in explicit list modes and whether the XDG path should be the primary home, are settled by later records (list modes use a modes table, the home is `.stratarc`); the earlier records are not edited.
+
+Naming and scope:
+
+- [rename to stratarc](2026-10-09-rename-to-stratarc.md)
+- [the stratarc name passed its checks with two caveats](2026-10-10-the-stratarc-name-passed-its-checks-with-two-caveats.md) (confirms the rename; the trademark registers it left open were checked where a search could be run)
+- [public package ships code only and no private integrations](2026-10-09-public-package-ships-code-only-and-no-private-integrations.md)
+- [one engine name](2026-10-09-one-engine-name.md)
+
+Source root and deployment:
+
+- [guards overlay package data](2026-10-09-guards-overlay-package-data.md)
+- [private extensions live in the source root](2026-10-09-private-extensions-live-in-the-source-root.md)
+- [no deploy branch guard unless environments declared](2026-10-09-no-deploy-branch-guard-unless-environments-declared.md)
+- [projects root from config](2026-10-09-projects-root-from-config.md)
+- [diff is a read-only full render](2026-10-09-diff-is-a-read-only-full-render.md)
+- [verify defines drift as a dry run](2026-10-09-verify-defines-drift-as-a-dry-run.md)
+- [sync verifies and rolls back on drift](2026-10-09-sync-verifies-and-rolls-back-on-drift.md)
+- [rollback places every adapter action line](2026-10-10-rollback-places-every-adapter-action-line.md), refines the verify and rollback record: relative and file-less lines are covered by the render's owned set
+- [sync records changes at its write points](2026-10-09-sync-records-changes-at-its-write-points.md)
+- [private checks gate deploy only when the source root opts in](2026-10-09-private-checks-gate-deploy-only-when-the-source-root-opts-in.md)
+- [the active source root is resolved in one place](2026-10-09-the-active-source-root-is-resolved-in-one-place.md)
+- [the source root private hook files are staged from the source only](2026-10-09-the-source-root-private-hook-files-are-staged-from-the-source-only.md) (narrows the staging exclusion in the two records on guards and private extensions)
+- [rendered workflows must run files the sync delivers](2026-10-09-rendered-workflows-must-run-files-the-sync-delivers.md)
+
+Settings, registries and state:
+
+- [layer order and provenance](2026-10-09-layer-order-and-provenance.md)
+- [explicit list modes in layers](2026-10-09-explicit-list-modes-in-layers.md)
+- [list modes use a modes table](2026-10-09-list-modes-use-a-modes-table.md), settles the open syntax point above
+- [list overrides never default their mode](2026-10-10-list-overrides-never-default-their-mode.md), settles the open default point in the two list mode records above
+- [home layout and safe writes](2026-10-09-home-layout-and-safe-writes.md)
+- [source root files keep their mode and the home stays private](2026-10-10-source-root-files-keep-their-mode-and-the-home-stays-private.md), refines the file modes in the home layout record
+- [the home is dot stratarc with an environment override](2026-10-09-the-home-is-dot-stratarc-with-an-environment-override.md), settles the open home point above
+- [adapter registry and support ranges](2026-10-09-adapter-registry-and-support-ranges.md)
+- [version detection runs in an isolated home](2026-10-09-version-detection-runs-in-an-isolated-home.md)
+- [providers hold secret references only](2026-10-09-providers-hold-secret-references-only.md)
+- [optional change log](2026-10-09-optional-change-log.md)
+
+Command line and interfaces:
+
+- [resource verb command grammar](2026-10-09-resource-verb-command-grammar.md)
+- [exit code map](2026-10-09-exit-code-map.md)
+- [message catalog with ids](2026-10-09-message-catalog-with-ids.md)
+- [read-only local API](2026-10-09-read-only-local-api.md)
+- [local API safeguards](2026-10-09-local-api-safeguards.md)
+- [terminal UI library is open](2026-10-09-terminal-ui-library-is-open.md), superseded by the Textual record below
+- [Textual is an optional extra for the terminal interface](2026-10-09-textual-is-an-optional-extra-for-the-terminal-interface.md)
+- [starc is the short command alias](2026-10-09-starc-is-the-short-command-alias.md), superseded by the drop record below
+- [drop the starc alias](2026-10-09-drop-the-starc-alias.md), supersedes the starc alias record: the command is `stratarc` only
+- [resource verbs fill the grammar gaps](2026-10-09-resource-verbs-fill-the-grammar-gaps.md)
+- [JSON accounts support set and unset](2026-10-10-json-accounts-support-set-and-unset.md), extends the account verbs in the gaps record
+- [explain follows the dispatch relay and flags are a layer](2026-10-09-explain-follows-the-dispatch-relay-and-flags-are-a-layer.md)
+- [the interface validates edits and keeps slow work off its thread](2026-10-09-the-interface-validates-edits-and-keeps-slow-work-off-its-thread.md)
+- [CLI design is delivered in ordered slices](2026-10-09-cli-design-is-delivered-in-ordered-slices.md)
+- [first run is a choice, not a scan](2026-10-09-first-run-is-a-choice-not-a-scan.md)
+
+Docs and tests:
+
+- [static docs site built from the repo](2026-10-09-static-docs-site-built-from-the-repo.md)
+- [example output is captured, not written](2026-10-09-example-output-is-captured-not-written.md)
+- [pytest is the only test runner](2026-10-09-pytest-is-the-only-test-runner.md)
+- [shellcheck gates at warning severity](2026-10-10-shellcheck-gates-at-warning-severity.md)
+- [the stack merges through its top pull request](2026-10-11-the-stack-merges-through-its-top-pull-request.md)
+- [new CLI tests carry mutation proofs](2026-10-09-new-cli-tests-carry-mutation-proofs.md)

stratarc-0.1.0/developer-docs/how-to-guides/README.md

@@ -0,0 +1,9 @@
+# how-to-guides
+
+How-to guides are recipes for a development goal. Each one assumes you have the repository set up and know your way around it, and gives the steps for one task with the minimum of explanation. They link to the reference pages for the details they skip and to the explanation pages for the reasons behind them.
+
+## pages
+
+- [add a runtime](add-a-runtime.md): write an adapter for another agent runtime, register it and test its output.
+- [run the tests](run-the-tests.md): the test suite, its markers, and the lint and scan checks CI runs.
+- [cut a release](cut-a-release.md): bump the version, settle the changelog, tag and publish.

stratarc-0.1.0/developer-docs/reference/README.md

@@ -0,0 +1,8 @@
+# reference
+
+Reference pages describe the codebase as it is: the layout of a source root, how packaged assets are found, the shape of each file. They are for looking something up while you change the code, so they are organised around the thing described, state facts without instruction, and aim to be complete. The how-to guides say what to do with these facts.
+
+## pages
+
+- [source layout](source-layout.md): the source root that `stratarc init` creates, what each file and directory holds and which runtimes consume it.
+- [package data](package-data.md): how the templates, schemas, hooks and git hooks under `stratarc/data/` are packaged and resolved through `importlib.resources`.

stratarc-0.1.0/developer-docs/tutorials/README.md

@@ -0,0 +1,7 @@
+# tutorials
+
+Tutorials are lessons for someone new to the codebase. Each one takes a reader through a development task from start to finish on one path, so the first contribution succeeds before the reader has to understand the whole repository. They link to the reference pages for detail rather than including it.
+
+## pages
+
+- [first contribution](first-contribution.md): from a fresh clone to a passing test suite, a small change and a pull request.

stratarc-0.1.0/docs/README.md

@@ -0,0 +1,23 @@
+# docs
+
+Documentation for people who use stratarc: you run the command, keep a source root and deploy it into your runtimes. It is arranged by the four [Diátaxis](https://diataxis.fr/) quadrants, so the folder a page sits in tells you what kind of page it is. If you change stratarc itself, the same shape exists under [developer-docs](../developer-docs/README.md).
+
+## tutorials
+
+Lessons that take you through a task from start to finish, for someone who has not done it before. Start with [getting started](tutorials/getting-started.md), which goes from an empty machine to a scaffolded source root and a first deployment. Index: [tutorials](tutorials/README.md).
+
+## how-to-guides
+
+Recipes for a specific goal, for someone who already knows the basics and wants the steps. [install](how-to-guides/install.md) covers every install method, [migrate existing config](how-to-guides/migrate-existing-config.md) brings a hand-maintained runtime directory under a source root, and [troubleshooting](how-to-guides/troubleshooting.md) matches a failure to its fix. Index: [how-to guides](how-to-guides/README.md).
+
+## reference
+
+Lookup pages that describe the machinery as it is, with no instruction attached. [cli](reference/cli.md) lists every subcommand and exit status, [configuration](reference/configuration.md) lists every key in `stratarc.toml` and the schemas that validate the JSON files, and [runtimes](reference/runtimes/README.md) names each supported runtime with a page per runtime: [claude](reference/runtimes/claude.md), [codex](reference/runtimes/codex.md), [cursor](reference/runtimes/cursor.md), [gemini](reference/runtimes/gemini.md) and [opencode](reference/runtimes/opencode.md). Index: [reference](reference/README.md).
+
+## explanation
+
+Discussion that gives background and reasons, for a reader who wants to understand rather than act. [security model](explanation/security-model.md) explains what stratarc protects against, what it trusts and what it leaves to the runtimes. Index: [explanation](explanation/README.md).
+
+## documentation-guide
+
+How this documentation is organised and how to add to it. [documentation guide](documentation-guide/README.md) says which folder a new page belongs in, and [feature documentation template](documentation-guide/feature-documentation-template.md) is the outline for a page that documents one feature end to end.

stratarc-0.1.0/docs/documentation-guide/README.md

@@ -0,0 +1,28 @@
+# documentation-guide
+
+This guide says where a document goes in this repository and what each kind of page is for, so a new page lands where its readers will look for it. The documentation follows [Diátaxis](https://diataxis.fr/): every page is one of four kinds, and the folder it sits in names the kind. Two trees hold the same five folders, [docs](../README.md) for people who use stratarc and [developer-docs](../../developer-docs/README.md) for people who change it. Pick the tree by audience first, then the folder by kind.
+
+## where-a-document-goes
+
+- `tutorials/`: a lesson that takes a newcomer through a task from start to finish on one path. Written to be followed in order; links out for detail instead of including it.
+- `how-to-guides/`: a recipe for one goal, for a reader who knows the basics. Steps first, explanation only where a step would otherwise surprise.
+- `reference/`: a description of the machinery as it is, structured around the thing described, complete and free of instruction.
+- `explanation/`: background and reasoning, read away from the keyboard; the place for why, for tradeoffs and for alternatives.
+- `documentation-guide/`: this folder, holding the conventions and templates for the documentation itself.
+
+A page that would need to be two of these is two pages. A reference table inside a tutorial moves to `reference/` and is linked; a paragraph of rationale inside a how-to guide moves to `explanation/`.
+
+## conventions
+
+- Filenames and headings are lowercase kebab-case; `README.md` keeps its name, and its H1 is the folder name.
+- Every page opens with a paragraph stating its purpose and what it covers, written for its audience.
+- Every `README.md` in a quadrant lists the pages in that quadrant with one line each, and the tree's top-level `README.md` has one paragraph per quadrant naming every page.
+- One line per paragraph and per list item; no hard-wrapped prose.
+- Every code fence carries a language tag.
+- No dashes as punctuation; use a comma, colon, semicolon, period or parentheses.
+- Links are relative paths within the repository.
+- No frontmatter is required. The provenance keys `models`, `providers` and `session-link` are forbidden and a CI check rejects them.
+
+## templates
+
+- [feature documentation template](feature-documentation-template.md): the outline for a page that documents one feature end to end.

stratarc-0.1.0/docs/explanation/README.md

@@ -0,0 +1,7 @@
+# explanation
+
+Explanation pages give background. They are for a reader who wants to understand stratarc rather than operate it: why it is shaped the way it is, what it trusts, what tradeoffs it makes and where its boundaries lie. They can be read away from the keyboard, they take a position, and they are the one place in the documentation where discussing alternatives is welcome.
+
+## pages
+
+- [security model](security-model.md): what stratarc protects against, how the detectors and hooks do it, what it trusts in a source root and what it leaves to the runtimes.

stratarc-0.1.0/docs/how-to-guides/README.md

@@ -0,0 +1,9 @@
+# how-to-guides
+
+How-to guides are recipes. Each one solves a specific problem for a reader who already knows what stratarc is and wants the steps, with the minimum of explanation along the way. They assume more than a tutorial and promise less: a guide gets you to one outcome, and links to the reference pages for the details it skips.
+
+## pages
+
+- [install](install.md): every supported way to install, upgrade and uninstall the command.
+- [migrate existing config](migrate-existing-config.md): bring a hand-maintained runtime directory under one source root without losing local changes.
+- [troubleshooting](troubleshooting.md): known failure modes matched to their fixes.

stratarc-0.1.0/docs/reference/README.md

@@ -0,0 +1,13 @@
+# reference
+
+Reference pages describe the machinery: the commands, the keys, the files each runtime receives. They are for looking something up while you work, so they are structured around the thing they describe rather than around a task, they state facts without instruction, and they aim to be complete rather than friendly. A reference page says what an option does; the how-to guides say when to reach for it.
+
+## pages
+
+- [cli](cli.md): every subcommand of the `stratarc` command with its arguments and exit statuses.
+- [config](config.md): the `stratarc config` commands, the layers and their precedence, the flags layer and the agent relay.
+- [resources](resources.md): the resource verbs for projects, runtimes, agents, accounts and sources.
+- [ui](ui.md): the terminal interface, its keys, editing, slow work and exit statuses.
+- [api](api.md): the read-only local API, its transport, routes, response envelope and limits.
+- [configuration](configuration.md): every key in `stratarc.toml`, the JSON Schemas that validate the source root, and the environment variables that override them.
+- [runtimes](runtimes/README.md): the supported runtimes, their default targets and one page per runtime: [claude](runtimes/claude.md), [codex](runtimes/codex.md), [cursor](runtimes/cursor.md), [gemini](runtimes/gemini.md) and [opencode](runtimes/opencode.md).

stratarc-0.1.0/docs/reference/runtimes/README.md

@@ -0,0 +1,13 @@
+# runtimes
+
+The agent runtimes stratarc targets, with the default directory it deploys each one to and a page per runtime describing the files stratarc writes for it. Each page is a reference: the file names, their formats and which part of the source root feeds each one. The pages fill in as the adapters are extracted.
+
+| runtime | default target | page |
+| --- | --- | --- |
+| Claude Code | `~/.claude/` | [claude](claude.md) |
+| Codex | `~/.codex/` | [codex](codex.md) |
+| Cursor | `~/.cursor/` | [cursor](cursor.md) |
+| Gemini CLI | `~/.gemini/` | [gemini](gemini.md) |
+| OpenCode | `~/.config/opencode/` | [opencode](opencode.md) |
+
+The target for each runtime is set in `stratarc.toml`; see [configuration](../configuration.md).

stratarc-0.1.0/docs/tutorials/README.md

@@ -0,0 +1,7 @@
+# tutorials
+
+Tutorials are lessons. Each one takes a reader who has not done the task before through it from start to finish, on one path, explaining only what that path needs. They exist so a new user succeeds at something real on the first try; they are not the place to look up an option or to understand a design, and they link out to the reference and explanation pages for that.
+
+## pages
+
+- [getting started](getting-started.md): from an empty machine to an installed command, a scaffolded source root, chosen runtimes and a first deployment.