Learning Castle Admission Schema

Canonical ID: /learning-castle/0117. Admission is the controlled promotion of a Scout-discovered candidate into registered Castle plumbing. A candidate does not become canonical because it is useful, popular, recently created or strongly linked. It becomes admitted only after ownership, evidence, collision, edge type, return, service/private boundaries, Keys, Portcullis and Validation all pass at the required confidence.

schema: learning_castle_admission
version: 0.1
castle_id: /learning-castle/0117
object_type: admission
purpose: controlled_candidate_promotion
source: /learning-castle/0116
registry: /learning-castle/0101
validation: /learning-castle/0107
may_register_node: true_after_pass
may_register_edge: true_after_pass
may_promote_canonical_owner: true_only_with_explicit_owner_evidence
may_auto_promote_from_popularity: false
may_auto_promote_from_keyword_match: false
canonical_return: /learning-castle/0019

Admission Record

admission_record:
  candidate_id
  source_node
  target_node
  candidate_type
  proposed_owner
  owner_status
  proposed_edge_type
  evidence_summary
  confidence
  collision_check
  service_boundary_check
  private_boundary_check
  required_keys
  portcullis_status
  return_status
  validation_status
  admission_status
  registry_action
  supersedes
  audit_note

admission_status:
  pending
  bounded
  admitted_noncanonical
  admitted_canonical
  rejected
  superseded

Admission Gates

GATE 1 owner:
  one_defensible_owner_or_explicit_bounded_owner

GATE 2 purpose:
  candidate_has_real_user_or_learning_job

GATE 3 collision:
  no_stronger_existing_route_already_does_same_job

GATE 4 edge:
  edge_type_matches_owner_scope_and_handoff

GATE 5 evidence:
  required_evidence_is_sufficient_for_requested_status

GATE 6 boundaries:
  service_and_private_boundaries_preserved

GATE 7 return:
  meaningful_return_exists_when_required

GATE 8 keys_and_portcullis:
  required_keys_valid
  no_hard_stop_triggered

GATE 9 validation:
  PASS_or_explicit_bounded_WARNING_for_noncanonical_admission

GATE 10 registry:
  register_without_silently_overwriting_existing_owner

Canonical Promotion Rules

admitted_noncanonical if:
  route_is_useful
  AND owner_is_clear
  AND candidate_should_exist
  BUT candidate_does_not_own_broader_intent

admitted_canonical only_if:
  primary_intent_is_distinct
  AND no_stronger_existing_owner_exists
  AND domain_boundary_is_explicit
  AND content_or_runtime_mass_justifies_owner_role
  AND inbound_and_return_plumbing_are_defined
  AND validation = PASS

never_promote_canonical because:
  newest_page
  highest_word_count
  strongest_keyword_match
  highest_internal_link_count
  commercial_priority
  aesthetic_symmetry

Registry Write Rules

when admitted_noncanonical:
  add_node_or_edge_record
  preserve_existing_canonical_owner
  declare_return
  declare_confidence

when admitted_canonical:
  add_explicit_canonical_owner_record
  declare_scope
  declare_superseded_owner_if_any
  preserve_history
  require_return_and_inbound_discovery

when rejected:
  do_not_add_live_route
  retain_audit_reason

when superseded:
  preserve_old_record_as_historical
  point_machine_resolution_to_new_verified_owner

Admission Failure Conditions

• owner conflict is unresolved;
• the proposed connection exists only because of shared terminology;
• a stronger existing route already performs the same job;
• the candidate would collapse knowledge into tuition-service ownership;
• the route exposes protected private runtime logic;
• a required Return Road is missing;
• the necessary Key is weakened, revoked or out of scope;
• a Portcullis hard stop is active;
• Validation fails.

Scout to Registry Runtime

SCOUT_DISCOVERED
-> CANDIDATE_PROPOSED
-> OWNER_RESOLVED_OR_BOUNDED
-> EDGE_CLASSIFIED
-> COLLISION_CHECKED
-> BOUNDARIES_CHECKED
-> RETURN_CHECKED
-> KEYS_CHECKED
-> PORTCULLIS_CHECKED
-> VALIDATED
-> ADMITTED_NONCANONICAL_OR_CANONICAL
-> REGISTRY_WRITTEN
-> SENTRY_MONITORS_LIVE_ROUTE
-> WATCHTOWER_OBSERVES_CHANGE

Machine Relationships

Admission receives proposals from the Scout, checks identity through the Node Schema, classifies movement through the Edge Schema, tests permission through the Key Schema and Portcullis Schema, checks return through the Return Schema, and requires Validation before writing to the Registry.

Discovery proposes. Validation judges. Admission promotes. Registry remembers.