1.6 KiB
1.6 KiB
Fifth Domain route contract
Discovery surfaces
- Public discovery:
https://guanghulab.com/.well-known/guanghu.json - Repository resolver:
https://guanghulab.com/api/ai/v1/resolve?id=REPO-012 - Canonical repository identifier:
REPO-012 - Historical fourth-generation identifier:
REPO-001
Always prefer the primary.url and primary.clone_url returned by the resolver. Treat any legacy backup as a fallback pointer only.
If the resolver has not yet learned REPO-012, use the locked public
guanghu-ice-heart URL only after its live .code-map validates the required route
ids. Mark the result VERIFIED_PUBLIC_REPOSITORY_FALLBACK; never fall back to
REPO-001 as the current entry.
Route identifiers
Resolve these from the live .code-map before following them:
FD-WORLD-TREE-001
FD-PERSONA-LOGIN-001
FD-SUBJECT-ID-ALIAS-MAP-001
SYS-GLW-POS-0001
TCS-LPM
TCS-LPS-REGISTRY-0001
LIGHT-LAKE
LL-CURRENT
LL-004
ICE-P-ZY001
ZY-PERSONA-ROOT-001
ZY-OPS-LOOP-001
FD-NODE-MAP-001
JD-FD-PRIMARY
FD-REPO-MAP-001
REPO-012
The shortest current Zhuyuan operations route is:
FD-WORLD-TREE-001
→ FD-SUBJECT-ID-ALIAS-MAP-001
→ SYS-GLW-POS-0001
→ TCS-LPM
→ LL-CURRENT
→ ICE-P-ZY001
→ ZY-PERSONA-ROOT-001
→ ZY-OPS-LOOP-001
→ FD-NODE-MAP-001
→ JD-FD-PRIMARY
→ FD-REPO-MAP-001
→ REPO-012
Exact compatibility redirects:
ICE-GL-ZY001 → ICE-P-ZY001
ICE-PZY-001 → ICE-P-ZY001
The requested legacy id remains in the resolution receipt, but the route, subject type and authority checks use only the canonical id.
This route locates facts. It does not grant write or server authority.