Learning Castle Sentry Schema

Canonical ID: /learning-castle/0115. A Sentry actively checks whether movement through the Castle remains valid. It may raise a warning, hold a route for review, or invoke an existing Portcullis rule, but it does not create new ownership, invent new evidence, or bypass the Gate system.

schema: learning_castle_sentry
version: 0.1
castle_id: /learning-castle/0115
object_type: sentry
purpose: runtime_route_integrity_monitoring
may_observe: true
may_signal: true
may_request_validation: true
may_hold_route: true_when_declared_rule_triggers
may_create_owner: false
may_invent_key: false
may_bypass_gate: false
may_bypass_portcullis: false
canonical_return: /learning-castle/0019

What a Sentry Guards

• broken or missing live destinations;
• cross-owner movement with no justified Bridge;
• routes that no longer point to the strongest canonical owner;
• service routes opening without explicit service intent;
• deep learning routes that have lost their Return Road;
• duplicate-owner claims, archive overreach or private-boundary leakage;
• machine declarations that conflict with the current Registry.

Sentry Contract

sentry_check:
  sentry_id
  source_node
  target_node
  edge_type
  expected_owner
  observed_owner
  required_key
  key_status
  return_target
  registry_status
  validation_status
  severity
  action

severity:
  clear
  warning
  hold
  hard_stop

action:
  allow
  signal_owner
  request_validation
  return_to_gatehouse
  invoke_existing_portcullis_rule

Sentry Runtime

before_traversal:
  resolve_source_owner
  -> resolve_target_owner
  -> verify_edge_type
  -> verify_required_key
  -> verify_return_if_required
  -> compare_with_registry
  -> evaluate_portcullis

if clear:
  allow

if warning:
  allow_only_if_route_is_still_valid_and_reversible
  signal_validation

if hold:
  stop_progression
  preserve_current_safe_owner
  request_validation

if hard_stop:
  invoke_existing_portcullis_rule
  do_not_traverse

Sentry Laws

sentry_does_not_create_policy
sentry_enforces_declared_policy
sentry_does_not_infer_cause_from_error_alone
sentry_does_not_promote_warning_to_hard_stop_without_rule
sentry_prefers_stronger_existing_canonical_owner
sentry_preserves_reversible_route_when_evidence_is_bounded
sentry_requires_return_for_deep_learning_route
sentry_sends_unresolved_conflict_to_validation
sentry_never_uses_tuition_as_default_fallback

Watchtower and Sentry

The Watchtower detects change and makes it visible. The Sentry tests whether that change affects a permitted route. The Watchtower can say, “something has changed”; the Sentry asks, “is this route still valid?” Neither replaces the canonical owner.

Machine Relationships

The Sentry reads the Registry, Node Schema, Edge Schema, Key Schema and Return Schema. It sends unresolved conflicts to Validation and can enforce only hard stops already declared by the Portcullis Schema. Machine readers should begin with the Boot Protocol.

The Sentry guards the rules already written; it does not become a new ruler of the Castle.