Repository navigation
Prepare Artifact Memory v0.1.4 release candidate #161
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.
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
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| """Provider-free Artifact Memory v0 reference runtime.""" | ||
|
|
||
| __version__ = "0.1.3" | ||
| __version__ = "0.1.4" | ||
| CONTRACT_VERSION = "v0" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,133 @@ | ||
| # Artifact Memory 0.1.4 release notes | ||
|
|
||
| Artifact Memory 0.1.4 is a private-vault onboarding and coordination-plane | ||
| update over v0.1.3. It adds a CLI-first path for bounded private operational | ||
| context, strict portable coordination records, local-first synchronization, | ||
| repository-bound freshness and scoping, and optional authenticated HTTP seams | ||
| for WITS coordination. | ||
|
|
||
| Release status is established only by an owner-signed annotated `v0.1.4` tag | ||
| and its verified release-manifest binding. This reviewed source document does | ||
| not claim that signing, publication, or attestation has occurred. | ||
|
|
||
| ## Private-vault onboarding | ||
|
|
||
| - The private-project guide and synthetic end-to-end fixture demonstrate | ||
| canonical records outside Git, replaceable SQLite projections, literal | ||
| search, bounded context-pack v4 export, and independent informational recall. | ||
| - Public fixtures remain wholly synthetic. Real vault records, generated | ||
| private views, credentials, raw conversations, and private topology remain | ||
| outside the public repository. | ||
| - The session-ledger importer converts a bounded dated Markdown done log into | ||
| deterministic private draft knowledge records. It rejects undated content, | ||
| oversized input, unsafe paths, immutable collisions, and credential-like | ||
| material before publishing any record. | ||
| - A generated projection or context pack remains a disposable view rather than | ||
| the canonical source. Storage does not imply encryption or backup, and | ||
| expiry does not establish deletion or global erasure. | ||
|
|
||
| ## Coordination records and local-first synchronization | ||
|
|
||
| - Strict TaskPacket, WorkReceipt, and AccessLabel schemas preserve portable | ||
| UUID identity, display-name provenance, typed evidence, predecessor | ||
| transitions, project-scoped permissions, and explicit no-authority fields. | ||
| - Revision identity remains the complete `(record_id, revision_digest)` pair. | ||
| Local and hub sets merge by union; different revisions of one logical record | ||
| coexist, while different bytes claiming the same complete pair are | ||
| quarantined rather than auto-resolved. | ||
| - Local append writes immutable coordination records and an outbox receipt | ||
| before network synchronization. Pending HTTP outcomes survive interruption | ||
| and require exact replay and acknowledgement before removal. | ||
| - Sync verifies complete authorized history, current task leaves, pair-set | ||
| digests, bounded pagination, continuation binding, and explicit exclusion | ||
| counts. Withheld identities are not disclosed by count-only receipts. | ||
| - Resource limits are checked before expensive parsing, canonicalization, or | ||
| uniqueness comparison. Unsafe files, links, reparse points, oversized state, | ||
| recursive JSON, out-of-profile canonical values, and interrupted local apply | ||
| fail with typed outcomes. | ||
|
|
||
| ## Repository identity, onboarding, context and freshness | ||
|
|
||
| - A committed `.agent-memory/repo.json` binds a repository to a stable UUID and | ||
| public-safe display name without treating a path, remote URL, hostname, or | ||
| checkout location as identity. | ||
| - Project onboarding validates the exact server-bound label and repository | ||
| identity, synchronizes the authorized set, and publishes immutable link, | ||
| kickoff, receipt, attempt, checkpoint, and recovery evidence transactionally. | ||
| - Scoped coordination context export uses the latest authorized projection and | ||
| effective AccessLabel. Grant/deny overlap, stale or ambiguous bindings, and | ||
| unsupported required extensions fail closed. | ||
| - Freshness is linked to an exact repository head. A kickoff pack may report | ||
| current, stale, dirty, unavailable, or unsupported evidence without claiming | ||
| global task truth. | ||
| - The exact-head hardening reviewed through PR #158 bounds retained | ||
| coordination reads, project-UUID sets, interrupted-apply recovery, and | ||
| canonicalization failure paths while preserving typed outcomes. | ||
| - Acceptance commands are escaped and rendered as untrusted informational | ||
| data. Artifact Memory never executes them or promotes them into tool policy. | ||
|
|
||
| ## Authenticated HTTP coordination seams | ||
|
|
||
| - The optional HTTP sync adapter uses standard-library TLS, refuses redirects | ||
| and URL credentials, ignores environment proxies, and permits cleartext only | ||
| for literal loopback fixtures. Bearers are supplied out of band through an | ||
| environment variable or in-memory API and are not persisted. | ||
| - The adapter verifies the expected logical hub, principal, exact AccessLabel, | ||
| sequential page receipts, complete authorized pair set, and the existing | ||
| local projection contract. It does not create a second coordination store. | ||
| - `artifact-memory claim` accepts one explicit exact open TaskPacket reference. | ||
| The authenticated hub alone mints and admits a claimed successor; the client | ||
| performs a second verified pull and reports only reference-bound evidence. | ||
| - Claim conflicts never select a fallback task. Lost or invalid responses are | ||
| unverified outcomes, and retries require the same original exact reference. | ||
| - The synthetic WITS bridge fixtures demonstrate protocol interoperability on | ||
| one machine. They do not establish deployed two-host operation, automatic | ||
| worker launch, production availability, or HTTP project onboarding. | ||
|
|
||
| ## Compatibility | ||
|
|
||
| - Published v0.1.0-v0.1.3 schemas retain their original meanings. Existing | ||
| record, context-pack, exchange, retention, release, search, and projection | ||
| contracts are not silently reinterpreted. | ||
| - Coordination schemas and CLI commands are additive and opt-in. Existing | ||
| provider-free record, projection, search, context, and release commands | ||
| remain available. | ||
| - The local-directory sync adapter and deterministic fixture behavior remain | ||
| supported. HTTP transport requires separately provisioned compatible WITS | ||
| routes, bearer capabilities, retained labels, origin/project ownership, and | ||
| server token policy. | ||
| - WITS's original authenticated round-trip v0 canary remains intentionally | ||
| pinned to the owner-signed Artifact Memory 0.1.0 package and rejects other | ||
| package versions. Run that historical canary in its dedicated 0.1.0 | ||
| environment; do not substitute 0.1.4 until WITS separately updates its | ||
| release binding and expected-version guard. The v0.1.4 coordination HTTP | ||
| fixtures are separate, explicitly pinned interoperability evidence. | ||
| - Repository onboarding writes a new strict public identity manifest only when | ||
| explicitly invoked. Existing repositories are not discovered or modified | ||
| automatically. | ||
|
|
||
| ## Authority and remaining limitations | ||
|
|
||
| Artifact Memory preserves and transports informational evidence. Records, | ||
| labels, receipts, context packs, kickoff packs, successful sync, and an | ||
| authenticated transport grant no execution, mutation, routing, disclosure, | ||
| credential, spending, deployment, approval, declassification, or merge | ||
| authority. A WITS Task Packet or HACP route remains a separate authority-bearing | ||
| contract enforced by its owning system. | ||
|
|
||
| The reference runtime is not a hosted coordination service, scheduler, agent | ||
| runner, credential manager, or global deletion system. HTTP project onboarding | ||
| and automatic worker launch remain unsupported. Integrity and provenance do not | ||
| establish authenticity or trust; unsigned evidence remains | ||
| `integrity-verified / issuer-unverified`. Generated indexes remain replaceable, | ||
| and private-vault custody, encryption, backup, retention, and disclosure policy | ||
| remain operator responsibilities. | ||
|
|
||
| ## Verification | ||
|
|
||
| Before publication, run the complete unit and conformance suites, public-safety | ||
| and public-JSON scans, installed-package smoke test, platform matrix, release | ||
| compatibility checks, deterministic candidate preparation, and the signed-tag | ||
| release-candidate verifier against the exact owner-approved commit. Publication | ||
| then triggers the separate keyless attestation workflow; that supplemental | ||
| workflow does not replace owner signing. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.