feat(sdk): procedural memory, precedence policy, adjudication reasons (v0.8.0) - #19
Merged
Merged
Conversation
Track the memory-thinkfleet steward + reasoning-via-memory workstream
(memory-thinkfleet #134/#135/#136).
- types: MemoryItemType.PROCEDURE; ProceduralMemoryMetadata + ProcedureStep;
MemoryReviewReason + ReviewQueueItem; MemoryProvenanceTier +
MemoryPrecedencePolicy + MemoryPrecedenceOverride.
- helper: renderProcedureContent() (identical to the engine renderer) +
DEFAULT_PRECEDENCE_POLICY.
- admin resource:
- createProcedure() — author a PROCEDURE (metadata + rendered content).
- getPrecedence() / setPrecedence() — read/write the precedence policy.
- listPendingReview() now returns ReviewQueueItem[] (each row tagged with
its reviewReason).
- http-client: add put() for the precedence PUT endpoint.
Additive, no breaking changes. v0.7.1 -> v0.8.0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Keeps the TS SDK in step with the merged memory-thinkfleet steward + reasoning-via-memory workstream (#134/#135/#136). Additive — no breaking changes. v0.7.1 → v0.8.0.
New surface
Procedural memory (#136)
MemoryItemType.PROCEDUREProceduralMemoryMetadata(goal,whenToUse,stepswith per-steppitfall,failureModes) +ProcedureSteprenderProcedureContent()— identical to the engine renderer, so client-authoredcontentmatches the serveradmin.createProcedure()— build metadata + rendered content and store as a PROCEDURE in one callPrecedence policy (#135)
MemoryProvenanceTier,MemoryPrecedencePolicy,MemoryPrecedenceOverride,DEFAULT_PRECEDENCE_POLICYadmin.getPrecedence()/admin.setPrecedence()(steward-gated PUT)Adjudication queue (#134)
MemoryReviewReason+ReviewQueueItemadmin.listPendingReview()now returnsReviewQueueItem[](each row tagged with itsreviewReason)Plumbing
HttpClient.put()added for the precedence endpointVerification
npm run typecheckclean;npm run buildproduces ESM + CJS + DTS; all new symbols present indist/index.d.ts.🤖 Generated with Claude Code