spec: CONTEXT-1 — decay defaults as RECOMMENDED guidance, canonical titles, corrected cross-spec citations

[JarbasAl]

Internal-purity refinement of OVOS-CONTEXT-1.

Changes

• Decay defaults (§5.3): an orchestrator MAY apply deployer-configurable default decay to entries written without an explicit turns_remaining/expires_at; any particular default values are tuning guidance — RECOMMENDED at most, never a conformance requirement.
• Decay/pipeline alignment (§4, §4.1): the decay model — pre-match prune, post-match turns_remaining decrement after every match round whether or not an intent matched, freshly written entries exempt from the decrement of the round that wrote them — is stated as the model OVOS-PIPELINE-1 §6.1 references (the PIPELINE-1 companion PR moves its flow diagram onto exactly this model).
• Canonical titles: OVOS-SESSION-1 cited as the Session Specification and OVOS-SESSION-2 as the Session Lifecycle and State Ownership Specification (intro and See-also).
• INTENT-4 citation (§6): the carriage of requires_context/excludes_context as additional registration-payload fields now cites INTENT-4 §5.2/§6.1 payloads plus the §5.3/§6.3 unknown-field-tolerance rule that makes the ride-along legal.
• Timeless wording (§9): the session-security "future specification" deferral restated as an out-of-scope statement.

CHANGELOG entry appended under the spec's current class. Version field unchanged: per VERSIONING.md it is a V1/V2 compatibility class, and these refinements do not change class.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1fd53d05-1604-4879-8ea5-eb7626f9e089

📥 Commits

Reviewing files that changed from the base of the PR and between 9003dcd and 5d0d340.

📒 Files selected for processing (2)

• CHANGELOG.md
• intent-context.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/intent-context

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}