docs(site): drop the internal-invariant clause from the landing intro

The intro stated per-task sandbox and credential isolation and daemon-owned
git to a reader who has no reason to act on it. Keep the event framing; the
enforcement detail stays in What runs where and ARCHITECTURE.md.

Regenerate docs/data/generated/docs.json with task docs:artifact.
This commit is contained in:
sam committed 2026-09-22 13:06:51 +10:00
1 parent 4cb732ace9
commit adebe1486a
2 files changed
+2 -3

No files matched your search

+1 -1
View File
@@ -4,7 +4,7 @@
"url": "/docs/",
"title": "Archie",
"section": "",
"body": "# Archie\n\nEvent Driven Agentic Automation.\n\n**archied** is a resident daemon. It polls a forge (GitHub, Gitea) for issues\nassigned or labelled to it, works each one in an isolated git worktree through a\nrouted workflow, and opens a pull request for human review.\n\nWork arrives as events. Each task runs in its own sandbox with a task-scoped\ncredential, and the daemon performs all git operations.\n\n## Start here\n\n- [First playbook](/docs/guides/first-playbook/) walks through getting one piece of\n work from an issue to a pull request.\n- [Architecture](/docs/architecture/) is the authority for settled design:\n the package map, the workflow engine, the task lifecycle, and the invariants\n that hold the whole thing together.\n\n## What runs where\n\nA deployment is one daemon plus the processes it talks to. The State Store is a\nstandalone process and owns the database outright; the daemon and gateway never\nopen it directly. Agents execute in containers that receive a task-scoped\ncredential, issued per task and revoked when the worktree is handed back.\n\nConfiguration lives at `${XDG_CONFIG_HOME:-~/.config}/archie/config.toml`.\nNothing in a working tree is load-bearing at runtime.\n\n## A note on these docs\n\nThis site is generated from the `docs/` directory of the\n[archie-core repository](https://github.com/samcharles93/archie-core) on every\nchange to `main`. The repository is the source; this site is a view of it. If\nthe two ever disagree, the repository is right.\n"
"body": "# Archie\n\nEvent Driven Agentic Automation.\n\n**archied** is a resident daemon. It polls a forge (GitHub, Gitea) for issues\nassigned or labelled to it, works each one in an isolated git worktree through a\nrouted workflow, and opens a pull request for human review.\n\nWork arrives as events.\n\n## Start here\n\n- [First playbook](/docs/guides/first-playbook/) walks through getting one piece of\n work from an issue to a pull request.\n- [Architecture](/docs/architecture/) is the authority for settled design:\n the package map, the workflow engine, the task lifecycle, and the invariants\n that hold the whole thing together.\n\n## What runs where\n\nA deployment is one daemon plus the processes it talks to. The State Store is a\nstandalone process and owns the database outright; the daemon and gateway never\nopen it directly. Agents execute in containers that receive a task-scoped\ncredential, issued per task and revoked when the worktree is handed back.\n\nConfiguration lives at `${XDG_CONFIG_HOME:-~/.config}/archie/config.toml`.\nNothing in a working tree is load-bearing at runtime.\n\n## A note on these docs\n\nThis site is generated from the `docs/` directory of the\n[archie-core repository](https://github.com/samcharles93/archie-core) on every\nchange to `main`. The repository is the source; this site is a view of it. If\nthe two ever disagree, the repository is right.\n"
},
{
"url": "/docs/architecture/",
+1 -2
View File
@@ -6,8 +6,7 @@ Event Driven Agentic Automation.
assigned or labelled to it, works each one in an isolated git worktree through a
routed workflow, and opens a pull request for human review.
Work arrives as events. Each task runs in its own sandbox with a task-scoped
credential, and the daemon performs all git operations.
Work arrives as events.
## Start here