Why Arcantry

Keep project meaning clear while agents help maintain it

Arcantry connects specifications, changelogs, task queues, agent guidance, and focused skills without confusing their roles. Inspect the whole project, automate repeated work, validate one boundary, or plan one controlled change without forcing a new repository shape.

See shared and private sources

One inspection finds active and shadowed configuration, source roles, visibility, versions, and compatibility.

Adopt only the boundary you need

Start without configuration, keep setup private, control the project externally, or track one shared contract.

Scale verification with risk

Combine static, automated, live, independent, and user checks only where they can change the decision.

01

Start with any project

An empty folder, a non-Git codebase, and a mature monorepo can all be inspected before Arcantry owns anything.

02

Keep meaning at the source

Todo captures incoming work, specifications hold accepted intent, changelogs explain releases, and skills automate procedures.

03

Stop stale changes before they land

Plans capture the inputs they expect, so a changed source stops application and asks for a fresh decision.

With and without

Replace repeated guesswork with one explicit project model

Area	Without Arcantry	With Arcantry
01 Discovery	Every tool scans the project again and builds a different picture of what exists.	One inspection returns the same map of present, missing, and configured sources.
02 Responsibility	OpenSpec, Changelog, todo.txt, and skills look like interchangeable files.	Each source keeps one role, owner, visibility, version, and management boundary.
03 Adoption	Trying one workflowcan require the framework's complete structure and configuration.	Connect one capability, keep it private, or adopt the complete project model.
04 Change	A script can discover, decide, and write before anyone sees the exact effect.	A reviewable plan separates the intended transition from later file writes.
05 Drift	A source changed after review can be overwritten by an older automation decision.	Arcantry checks the expected inputs and stops when the project changed.
06 Automation	Tools duplicate compatibility rules and disagree about project boundaries.	People and tools read the same source map, evidence, and boundaries.

Explore Arcantry

Go from the project map to the decision you need

Project knowledge stack

Understand the model before changing anything

See why authority, release projections, queues, skills, private state, and integrity evidence stay separate even when one tool can inspect them together.

Understand the source roles

1. Inspect a project safelyGet the source map without creating or rewriting project files
2. Choose the right footprintCompare zero-footprint, external, tracked, selective, and full integration
3. Make queues reviewablePreview shared or private todo.txt changes before writing them
4. Give an agent one procedureChoose a focused skill in user or repository scope

Adoption strategies

Prefer complete integration, keep selective use available

Arcantry is most valuable when it can describe the complete project knowledge stack. That is the recommended destination for both new and existing projects, but every source and capability remains independently adoptable.

1. 01For personal or workstation-specific project context

   Keep adoption private

   Use `.local/arcantry.toml`, private agent guidance, and independent private sources without tracking them.

   Benefit: project-aware tools with private state kept off Git.Adopt private scope
2. 02For focused agent-user collaboration

   Link selected skills

   Choose focused self-improvement, repository safety, or content safety procedures in user or repository scope.

   Benefit: repeatable workflows consume less context and keep clear approval boundaries.Explore the skill families
3. 03For teams sharing the project contract

   Adopt shared scope

   Track configuration and agent guidance while keeping private sources independent under `.local`.

   Benefit: collaborators and automation start from the same explicit boundary.Adopt shared scope

Compose your setup

See where each source lives

Common setups

Shared + privateShare team files. Keep personal guidance and tasks private.RecommendedPrivate projectKeep project knowledge in .local, outside Git.Selected sourcesConnect only the sources this project needs.

ComputerAvailable across projects.

• SkillsReusable procedures.

RepositoryTracked in Git.

• SkillsReusable procedures.Project
• GuidanceAgent instructions.Project
• todo.txtTask queue.Project
• OpenSpecRequirements and changes.Manage
• ChangelogRelease history.Manage

Private projectStored in .local, outside Git.

• GuidanceAgent instructions.Private
• todo.txtTask queue.Private
• OpenSpecRequirements and changes.
• ChangelogRelease history.

Your setup

Every project has different boundaries.Build a setup that keeps its knowledge safe.

Configure your setupLearn moreExplore the details