Skip to content

docs: establish governed public repository surface - #5

Draft
seonghobae wants to merge 2 commits into
mainfrom
codex/public-surface-embedrelay-20260920
Draft

seonghobae wants to merge 2 commits into
mainfrom
codex/public-surface-embedrelay-20260920

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Outcome

Create a bounded repository-facing public surface for EmbedRelay without moving product-domain, ontology, catalog, routing, or authorization authority into this repository.

Exact source

  • protected base: main@816dcacd4fc1903d91c5cae9b77e37e21811a78d
  • exact head: 0fc8fb34341c43876953e9d72d97060145d61f7f
  • compare: ahead 2 / behind 0; merge base equals protected main
  • changed paths: README.md, docs/index.md only
  • README blob: cd846c3744ab1fdc9034d5c3d4097bf33b584211
  • public-overview blob: 95535ac941caa010ec21189cd62d569df565f262

Responsibility boundary

EmbedRelay owns reusable embedding-space identity, compatibility validation, provenance, migration, cutover, rollback, and verification contracts. Product repositories retain domain truth, Ubiquitous Language, source data, authorization, and releases. ConceptWeave retains ontology generation/publication, semantic-data-portal retains catalog/governance/search/serving, and contextual-orchestrator retains provider discovery/routing.

Verification

Fresh exact-head readback confirms one exact DeepWiki badge, valid Markdown front matter, canonical repository/README/DeepWiki navigation, the stated authority boundary, and exactly the two intended paths. This is source evidence only.

Keep Draft until exact-head hosted Checks and independent review settle. Protected-main integration, repository settings reconciliation, deployment, live HTTP 200, and rendered-source verification remain prerequisites before GitHub Pages publication is claimed. No force-push, bypass, self-approval, release, or predecessor-head evidence transfer.

@coderabbitai

coderabbitai Bot commented Sep 19, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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.

Copy link
Copy Markdown
Contributor Author

2026-09-20 exact-head public-surface evidence

  • exact head: 0fc8fb34341c43876953e9d72d97060145d61f7f
  • protected base: main@816dcacd4fc1903d91c5cae9b77e37e21811a78d
  • compare: ahead 2 / behind 0; merge base equals protected main
  • changed paths: exactly README.md and docs/index.md
  • blobs: README cd846c3744ab1fdc9034d5c3d4097bf33b584211; overview 95535ac941caa010ec21189cd62d569df565f262
  • exact source readback: one linked ContextualWisdomLab DeepWiki badge, Markdown front matter, canonical navigation, and explicit domain/ontology/catalog/routing/authorization boundaries present
  • lifecycle: Draft; mergeable=true; unresolved review threads=0; APPROVED reviews=0
  • current exact-head runs: SAST Semgrep 35472483391, CodeQL PR 35472483401, Security Scan 35472483416; all queued

Central desired state is recorded at ContextualWisdomLab/.github#2110 head fedc301ee0df3b2efeea6fd56b2f699a4ad0893b. This does not transfer central evidence or publish from this Draft head. Protected-main integration, settings reconciliation, deployment, live HTTP 200, and rendered-source verification remain required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation priority: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant