Skip to content

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

Open
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-context
Open

spec: CONTEXT-1 — decay defaults as RECOMMENDED guidance, canonical titles, corrected cross-spec citations#118
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-context

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

🤖 Auto-generated by Claude Fable 5 (claude-fable-5) via Claude Code — NOT human-reviewed. Verify before acting. Cross-spec citations were model-verified against dev source; behavior-change sections need owner judgment.

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 spec: PIPELINE-1 — resolve-lang-once, timeout defaults, match-phase liveness, reserved-name stamping suppression #109, already merged, moved 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.
  • Citation fixes: intro MSG-1 forward citation corrected from §5.3 to §5.1 (the derivation MSG-1 §5 actually defines under that heading); SESSION-1 field-registry citation tightened from bare §2 to §2.2.
  • CHANGELOG pathway model: the "Initial draft" bullet's mutation-pathways summary, stale since the §5 rewrite, now names the actual §5.1 (pipeline-plugin Match.updated_session), §5.2 (transformer in-place write), §5.3 (skill/handler ovos.session.sync entry-level merge) model instead of the superseded "skill bus events / engine auto-population / orchestrator sweep" description.

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

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 36 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: 4910833d-edb5-4e5d-9cde-98f98ade8509

📥 Commits

Reviewing files that changed from the base of the PR and between 1d3622b and 8676941.

📒 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

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

@JarbasAl
JarbasAl marked this pull request as ready for review July 16, 2026 07:21
JarbasAl added a commit that referenced this pull request Aug 4, 2026
…angelog pathway model

Fixes three latent citation issues found in audit of PR #118 (all
prior hunks KEEP, no rework needed there):

- Intro cited the forward() derivation backing the ovos.session.sync
  mutation pathway as MSG-1 §5.3; MSG-1 §5 actually defines forward
  under §5.1 (§5.3 is response()). Corrected.
- SESSION-1 field-registry citation tightened from bare §2 to §2.2,
  the actual field-registry subsection, for consistency with this
  spec's other precise cross-references.
- CHANGELOG's "Initial draft" bullet still described a superseded
  mutation-pathway model (skill bus events; engine auto-population on
  match; orchestrator sweep on session close). Rewritten to name the
  actual §5.1-§5.3 model: pipeline-plugin Match.updated_session
  applied post-match-pre-dispatch, transformer in-place hook writes,
  and skill/handler entry-level merge via ovos.session.sync.
@JarbasAl
JarbasAl force-pushed the spec/intent-context branch from 5d0d340 to 4a2bf9e Compare August 4, 2026 11:15
…itles, corrected cross-spec citations

Squashed from:
- spec: CONTEXT-1 — forward cited as MSG-1 §5.1; registry cite §2.2; changelog pathway model
- docs: CONTEXT-1 consistency review — decay defaults as guidance, canonical titles, corrected citations

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@JarbasAl
JarbasAl force-pushed the spec/intent-context branch from 4a2bf9e to 8676941 Compare August 4, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant