Skip to content

docs(readme): rewrite around what an artifact is and how to boot it #25

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
TheGreatAxios merged 2 commits into from
Sep 27, 2026
Merged

docs(readme): rewrite around what an artifact is and how to boot it #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e30e7ba
docs(readme): rewrite around what an artifact is and how to boot it
TheGreatAxios Sep 25, 2026
75e8ad1
docs: fold the architecture notes out of the repo root
TheGreatAxios Sep 25, 2026
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
0 SECURITY.md → .github/SECURITY.md
View file
Open in desktop
File renamed without changes.
352 changes: 0 additions & 352 deletions ARCHITECTURE.md
View file
Open in desktop

This file was deleted.

6 changes: 3 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,8 +84,8 @@ always called out under their own heading.
`createArtifact` is a public, unconditional insert used directly by the
import route, uploads, and `artifact_link_file`, and a shared title across
independent creates on those paths is normal, not a bug a schema
constraint should forbid. See the "Find-or-version" section of
ARCHITECTURE.md.
constraint should forbid. See the find-or-version notes in
CONTRIBUTING.md.

### Changed

Expand All @@ -106,7 +106,7 @@ always called out under their own heading.
`examples/reference-host` now wires a real one (`grantOwnership`) against
Interchange's own `grant` table, and its default `requireGrant` is the
platform's real `createRequireGrant` over that table rather than a
default-allow stub — see ARCHITECTURE.md's "Grant provisioning" section.
default-allow stub — see CONTRIBUTING.md's "Grant provisioning" section.
- Single-artifact write routes (`POST .../versions`, `POST .../archive`,
`POST .../unarchive`) now resolve existence/tenant/skill-draft (the same
check `loadScoped` does) BEFORE running `requireGrant`, not after. A real,
Expand Down
Loading
Loading