Repository navigation
docs: archive notice; superseded by Assay #115
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,8 @@ | ||
| > [!IMPORTANT] | ||
| > **Archived 2026-10-15.** Superseded by [Assay](https://github.com/shmindmaster/assay), a reference architecture for deterministic agent control. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When users enter through the npm package, Useful? React with 👍 / 👎. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Declaring GitPin archived changes its operational state, but AGENTS.md reference: AGENTS.md:L24-L24 Useful? React with 👍 / 👎. |
||
| > Why: the same agent writes both the change and its evidence manifest, so the gate proves coverage and hash pinning, not that a claim is true. Assay moves the decision into deterministic code instead. | ||
| > The last release, 0.6.4, stays on npm. The rest of this README is unchanged. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This sentence now asserts that 0.6.4 remains available on npm, while the same README’s Status section still says the tree describes 0.6.4 “without asserting publication status” and instructs readers to check each channel independently. Since README is the publishing entry point, these mutually incompatible instructions make the archive status ambiguous; update the Status section or avoid asserting registry availability here. AGENTS.md reference: AGENTS.md:L13-L15 Useful? React with 👍 / 👎. |
||
|
|
||
| <div align="center"> | ||
|
|
||
| <img src="docs/media/social-preview.png" alt="GitPin: agent pull requests must show exact evidence before they merge." width="100%"> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The claim says the notice includes “one line on why,” but this locator ends at README line 2 while the rationale is on line 3. The gate therefore reports this claim as evidence-verified even though its cited slice does not contain the asserted explanation; extend the range through line 3 and recompute the hash, or remove that clause from the statement.
Useful? React with 👍 / 👎.