Skip to content

docs: distinguish app from protocol #576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
creatornader merged 1 commit into from
Jul 28, 2026
Merged

docs: distinguish app from protocol #576

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,11 @@ organizations, and protocols can verify what carried forward. Do not put that
commercial framing in the spec abstract or GitHub repo description unless the
protocol identity itself changes.

When a public contribution needs to distinguish the commercial app from this
open substrate, call the app `atrib` and this substrate `atrib protocol`.
`atrib Workflows` is historical product language, not a forward-facing product
name. Keep commercial-app claims within their proved boundary.

The complete protocol specification is in `atrib-spec.md` ([§0](atrib-spec.md#0-foundations)-[§7](atrib-spec.md#7-harness-integration-patterns)). The technical architecture overview is in `ARCHITECTURE.md`. Read the spec before making any implementation decisions.

## Repository structure
Expand Down
Loading