Filing gate: ① a defect, class (c), a teaching error in published text an AI author reads. reach: the exception for wrong text that ships: skills/** goes out with npx skills add. docs/NORTH-STAR.md priority rule 4: 「写给 AI 的文档与 skills 说错一句,等于产品缺陷」. Filed by domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM, seat post #18549), from the #20274 agent.memory dev report 5953769101 (out-of-scope finding 1). It is the memory half of the sentence whose guardrails half #21288 fixed through PR #21302. ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.
Who acts on it: the skills/** lane. It is a Tier H surface and lands by human approval in its own PR. It should ship in the same release as PR #21413. Neither publishes on merge: the release is the Version Packages PR.
Dedupe: the ~1,000 most recently updated issues and PRs here, open and closed, were listed by REST and grepped for declared only or objectstack-ai/SKILL.md together with memory. That gave 4 hits:
None carries the memory clause after the change.
The position (read at main)
skills/objectstack-ai/SKILL.md:311-313, Common Pitfalls 1: "… but it is a limit, not an approval; memory is declared only — no runtime reads it."
What PR #21413 makes true (ruling A′ 5950198150 on #20274)
agent.memory is enforced by the cloud AI runtime. The agent.memory ledger row is live (cloud ef5a4344, compileAgentMemory, attested by 5946891697).
- When
longTerm.enabled is true, maxEntries and reflectionInterval are required. reflectionInterval without an enabled longTerm is refused.
longTerm.store is retired: storage is the platform's.
The fix
Rewrite the clause to say that memory is enforced by the AI runtime ☁️: long-term notes are recalled and reflected on, with maxEntries and reflectionInterval required when longTerm.enabled, and no storage backend to choose. Keep the sentence's point that none of these is a gate. Nothing else in the pitfall changes.
Generated by Claude Code
Filing gate: ① a defect, class (c), a teaching error in published text an AI author reads.
reach:the exception for wrong text that ships:skills/**goes out withnpx skills add.docs/NORTH-STAR.mdpriority rule 4: 「写给 AI 的文档与 skills 说错一句,等于产品缺陷」. Filed bydomain:specseat 2 (session_01YDt3PzwfrkuFzUBF89WPmM, seat post #18549), from the #20274agent.memorydev report5953769101(out-of-scope finding 1). It is thememoryhalf of the sentence whoseguardrailshalf #21288 fixed through PR #21302. ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.Who acts on it: the
skills/**lane. It is a Tier H surface and lands by human approval in its own PR. It should ship in the same release as PR #21413. Neither publishes on merge: the release is the Version Packages PR.Dedupe: the ~1,000 most recently updated issues and PRs here, open and closed, were listed by REST and grepped for
declared onlyorobjectstack-ai/SKILL.mdtogether withmemory. That gave 4 hits:guardrailsflip);guardrailsas unenforced andoutputSchemaas never validated; the cloud AI runtime now enforces both (objectstack-ai SKILL.md, actions.mdx) #21288 (closedcompleted; theguardrails/outputSchematext);memoryclause becausememorywas then unenforced);None carries the
memoryclause after the change.The position (read at
main)skills/objectstack-ai/SKILL.md:311-313, Common Pitfalls 1: "… but it is a limit, not an approval;memoryis declared only — no runtime reads it."What PR #21413 makes true (ruling A′
5950198150on #20274)agent.memoryis enforced by the cloud AI runtime. Theagent.memoryledger row islive(cloudef5a4344,compileAgentMemory, attested by5946891697).longTerm.enabledis true,maxEntriesandreflectionIntervalare required.reflectionIntervalwithout an enabledlongTermis refused.longTerm.storeis retired: storage is the platform's.The fix
Rewrite the clause to say that
memoryis enforced by the AI runtime ☁️: long-term notes are recalled and reflected on, withmaxEntriesandreflectionIntervalrequired whenlongTerm.enabled, and no storage backend to choose. Keep the sentence's point that none of these is a gate. Nothing else in the pitfall changes.Generated by Claude Code