Skip to content

Define public route readiness before eligibility - #244

Merged
RobLe3 merged 1 commit into
mainfrom
codex/supervised-route-readiness
Aug 28, 2026
Merged

RobLe3 merged 1 commit into
mainfrom
codex/supervised-route-readiness

Conversation

@RobLe3

@RobLe3 RobLe3 commented Aug 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • distinguish a created tunnel URL from a serving, externally verified route
  • require active /iicp/health evidence before an external tunnel can receive credentials or become discoverable
  • add the implementation-neutral lifecycle scenario and a pre-1.0 provider-route-readiness capability

No new wire fields, authority semantics, release number, deployment or 1.0 claim are introduced.

Validation

  • python3 tools/test_directory_state_semantics.py
  • python3 tools/check_pre1_feature_baseline.py
  • python3 tools/manage_release_closure.py --prepare && python3 tools/manage_release_closure.py --check
  • root local CI preflight for spec-only

Closes #243

@RobLe3
RobLe3 merged commit 0a5d666 into main Aug 28, 2026
2 checks passed
@RobLe3
RobLe3 deleted the codex/supervised-route-readiness branch August 28, 2026 15:57
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.

[pre-1.0][conformance] Bind registration, route readiness and dispatch eligibility

1 participant