Skip to content

crosswalk(sint): promote entity_continuity to signal_types (follows sint-protocol #178)#45

Merged
aeoess merged 1 commit intomainfrom
feat/sint-crosswalk-migration-attestation
Apr 23, 2026
Merged

crosswalk(sint): promote entity_continuity to signal_types (follows sint-protocol #178)#45
aeoess merged 1 commit intomainfrom
feat/sint-crosswalk-migration-attestation

Conversation

@aeoess
Copy link
Copy Markdown
Owner

@aeoess aeoess commented Apr 23, 2026

Summary

Follow-through on the commitment made in sint-ai/sint-protocol#178 — when pshkv shipped migrationAttestation as a structural precondition on ConstraintEnvelope, the crosswalk/sint.yaml entry for entity_continuity needed to move from proposed_signal_type_alignment (marked no_mapping) to the main signal_types section (marked structural), because SINT now implements the vocabulary.yaml entity_continuity contract at a real composition point APS issuers can compose against.

Changes

  • entity_continuity promoted. Moved from proposed_signal_type_alignment to signal_types. Match: structural. Field: constraintEnvelope.migrationAttestation. Definition cites SBR-002 alignment, 5 validation rules, 8 test cases, forward-compatibility across envelope versions.
  • Cross-spec convergence noted. The composition point is explicit: when a SINT ConstraintEnvelope is attached to a delegation, the migration-attestation check becomes a precondition on every action the envelope governs. Notes also reference the mutation_boundary descriptor from pending vocab PR feat(vocab): add measurement_point to entity_continuity descriptor #43 (nutstrut's measurement_point proposal), reinforcing the cross-spec convergence on the execution-boundary framing.
  • consent_provenance upgraded. Stays in proposed_signal_type_alignment for now since vocabulary.yaml hasn't added it canonically yet. Match upgraded from partial to still partial (the validator's allowed set doesn't include close_match, which would be more accurate). Notes now point at policy_bundle.consent_chain + APS delegation chain as the composition surface, with a v1.1 path via sint-protocol PR #168.
  • Metadata updated. last_reviewed bumped to 2026-04-23. New refresh note documenting the promotion.

Why this is a crosswalk PR and not a vocabulary change

This PR only edits crosswalk/sint.yaml. It does not propose any change to vocabulary.yaml. The entity_continuity signal_type was already canonical (merged via PR #28 on Apr 17). This PR just reflects that SINT now implements it.

Validator

node scripts/validate-crosswalks.js

Zero errors on sint.yaml. The 5 errors the validator reports are all in _test-invalid.yaml (intentional negative fixtures) and pre-date this PR.

Review checklist (5-check protocol)

  1. Identity. SINT maintainer is @pshkv, confirmed by crosswalk_metadata.authored_by and live at sint-ai/sint-protocol PR #178.
  2. Format. Signal_types section structure followed: canonical, sint_term, sint_field, sint_definition, match, notes.
  3. Substance. PR #178 diff shows ConstraintEnvelopeMigrationAttestation interface in packages/core/src/types/protocol.ts, 5 validation rules in packages/core/src/constraint-language.ts, 8 new test cases in packages/core/__tests__/constraint-language.test.ts. All verifiable.
  4. Scope. Only edits the existing sint.yaml entry + reorganizes within the file. Does not touch any other crosswalk, does not touch vocabulary.yaml.
  5. Reversibility. Single-file YAML edit, trivially reversible.

Cross-refs

…tural match (shipped in sint-protocol PR #178)

Illya shipped migrationAttestation as a structural precondition on ConstraintEnvelope at sint-ai/sint-protocol#178: when present, the envelope validates only if continuityVerified === true with all four shape fields populated. This makes entity_continuity a scope-grant gate at the execution boundary, not an advisory signal.

Changes:
- Moved entity_continuity from proposed_signal_type_alignment to signal_types
- Match: structural (PR #178 implements the vocabulary.yaml entity_continuity contract at a composition point APS can rely on)
- Field: constraintEnvelope.migrationAttestation with sint_definition citing SBR-002 alignment, 5 validation rules, 8 test cases
- Notes cite the mutation_boundary descriptor from pending vocab PR #43, reinforcing the cross-spec convergence on the execution-boundary framing
- consent_provenance stays in proposed_signal_type_alignment, upgraded to partial with composition note pointing at policy_bundle.consent_chain + APS delegation chain
- Updated last_reviewed to 2026-04-23 and added refresh note

Validator: 0 errors on sint.yaml (only pre-existing _test-invalid.yaml errors remain).
@aeoess aeoess merged commit 98d73d9 into main Apr 23, 2026
@aeoess aeoess deleted the feat/sint-crosswalk-migration-attestation branch April 23, 2026 23:10
nutstrut pushed a commit to nutstrut/agent-governance-vocabulary that referenced this pull request May 4, 2026
…tural match (shipped in sint-protocol PR #178) (aeoess#45)

Illya shipped migrationAttestation as a structural precondition on ConstraintEnvelope at sint-ai/sint-protocol#178: when present, the envelope validates only if continuityVerified === true with all four shape fields populated. This makes entity_continuity a scope-grant gate at the execution boundary, not an advisory signal.

Changes:
- Moved entity_continuity from proposed_signal_type_alignment to signal_types
- Match: structural (PR #178 implements the vocabulary.yaml entity_continuity contract at a composition point APS can rely on)
- Field: constraintEnvelope.migrationAttestation with sint_definition citing SBR-002 alignment, 5 validation rules, 8 test cases
- Notes cite the mutation_boundary descriptor from pending vocab PR aeoess#43, reinforcing the cross-spec convergence on the execution-boundary framing
- consent_provenance stays in proposed_signal_type_alignment, upgraded to partial with composition note pointing at policy_bundle.consent_chain + APS delegation chain
- Updated last_reviewed to 2026-04-23 and added refresh note

Validator: 0 errors on sint.yaml (only pre-existing _test-invalid.yaml errors remain).
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