NEXUS — Research & Joint Ventures Authority Coordination Record¶
Authority codename: NEXUS (Research Center, research_center_ext, v2.1.0+)
FCC owner persona: RHL (Research Handoff Liaison) — src/fcc/data/personas/research_handoff_liaison.yaml
FCC peer liaison: IHL (Innovation Handoff Liaison) — parallel coordination into the PHOENIX patent lane
Active handoffs: two industry papers queued under docs/papers/, joint-venture experimentation pipeline
Authority role¶
NEXUS is the ecosystem's Research & Joint Ventures Authority. Within the tri-authority coordination model that FCC v1.7.1 codifies, NEXUS owns the research lane: academic-paper authorship contracts, empirical methodology, venue selection, reproducibility evidence, and cross-institution joint-venture experimentation. It is also the authoritative inventory owner for port allocations and ecosystem project registration (vendored into FCC as src/fcc/data/ecosystem/port_allocation.yaml and ecosystem_projects.yaml, drift-checked by tests/test_ecosystem_registry_drift.py).
FCC depends on NEXUS because FCC ships architectural evidence — abstracts, outlines, UML-level figures, citation bundles, persona discipline — but does not itself run experiments. NEXUS extends FCC seed papers with methodology, empirical results, and venue submission. FCC also depends on NEXUS for the authoritative port/project registry: any change in FCC's vendored registry must reconcile against the NEXUS source-of-truth via SHA256 drift CI.
In joint-venture mode (cross-institution research funded by multiple partners), NEXUS is the designated coordination node — it holds the JV governance artifacts (Lead Charter, Critique Protocol, JV Standard) and negotiates author-order, licensing posture, and dataset-sharing agreements across partner institutions. FCC contributes persona-level JV governance (the jv_governance and jv_collaboration persona categories, six personas each) but NEXUS is the convening authority.
Coordination cadence¶
- Weekly: RHL holds a weekly sync with NEXUS research counterparts across active PI windows
- Per-PI (quarterly): RHL ships the next round of paper seed artifacts; NEXUS extends prior-PI seeds toward venue submission
- Per-release (FCC patch cadence): FCC's weekly
patent-mirror-check.ymlsibling (paper-handoff variant, v1.4.4+) verifies backlink integrity between FCCdocs/papers/and NEXUSdocs/papers/<name>-fcc-handoff/ - Ad-hoc: drift between vendored and authoritative port/project registries opens an auto-assigned GitHub issue on the NEXUS side
PI alignments in flight at v1.7.1:
- RC PI-2026-Q3 — Quantum-Locality paper (target venues: ACM SIGMOD, IEEE Quantum Week, ICML Workshop on Quantum AI)
- RC PI-2026-Q4 — Zachman-R.I.S.C.E.A.R.+SAFe paper (target venues: IEEE Software, ACM SEN, XP/Agile 2026)
Handoff artifacts¶
FCC hands to NEXUS (per paper):
- Abstract (150-250 words)
- Outline (H1-H3 sections with 1-3 sentence section abstracts)
- Citation bundle (minimum 20 references per paper)
- Architectural evidence — UML figures, ADR references, code-path citations
- Reproducibility manifest — datasheet (Gebru et al.) + model card (Mitchell et al.) + evidence graph
NEXUS hands back to FCC:
- Experimental methodology section draft
- Results section (empirical data, statistical analysis)
- Venue-specific formatting + submission coordination output
- Author-order negotiation record (typically alphabetical within-institution, FCC first-authored for FCC-originated contributions)
- Post-publication SHA-anchored
<nexus-repo>/docs/papers/<name>-fcc-handoff/entry for drift CI
Joint ownership: both parties co-author; both hold CC-BY-4.0 on paper text and MIT license on reference implementations. No proprietary-license artifacts cross the FCC ↔ NEXUS boundary.
Queued handoffs (v1.7.1 state)¶
Paper #1 — Quantum-Locality
- FCC source path:
docs/papers/quantum-locality/ - Title (working): Quantum-Locality Constraints on Multi-Agent Event Routing
- Abstract scope: Applies locality arguments from quantum information theory to per-lane event routing in the FCC dual-bus architecture (v1.4.2). Argues that cross-lane correlations obey locality bounds analogous to Bell-inequality constraints, with observable consequences for observability and back-pressure design.
- NEXUS extension required: formal derivation of locality-preserving routing invariants; simulation of cross-lane correlations under synthetic workloads; empirical measurement on FCC reference deployment
- Handoff target: RC PI-2026-Q3
- Reproducibility manifest:
docs/papers/quantum-locality/manifests/
Paper #2 — Zachman-R.I.S.C.E.A.R.+SAFe
- FCC source path:
docs/papers/zachman-riscear-safe/ - Title (working): Unifying Zachman, R.I.S.C.E.A.R., and SAFe: A Three-Axis Framework for Multi-Agent Governance
- Abstract scope: Proposes a composable three-axis framework in which the Zachman cube (row × column) indexes architectural context, the R.I.S.C.E.A.R. 10-component spec indexes agent persona discipline, and SAFe PI planning indexes cadence. Evaluates the composition on 110+ FCC personas across the constellation ecosystem.
- NEXUS extension required: comparative evaluation vs TOGAF-only, SAFe-only, and agent-framework-only baselines; empirical scorecard across 10 constellation projects; practitioner survey (N ≥ 40)
- Handoff target: RC PI-2026-Q4
- Reproducibility manifest:
docs/papers/zachman-riscear-safe/manifests/
Cross-repo contracts¶
FCC modules and files NEXUS touches or validates:
| FCC path | NEXUS concern |
|---|---|
docs/papers/quantum-locality/ |
seed artifacts for Paper #1 (extended at RC PI-2026-Q3) |
docs/papers/zachman-riscear-safe/ |
seed artifacts for Paper #2 (extended at RC PI-2026-Q4) |
src/fcc/data/ecosystem/port_allocation.yaml |
vendored mirror of authoritative NEXUS registry; SHA256-drift-checked in CI |
src/fcc/data/ecosystem/ecosystem_projects.yaml |
vendored mirror of authoritative NEXUS inventory; SHA256-drift-checked in CI |
tests/test_ecosystem_registry_drift.py |
CI test that pins the vendored registries to NEXUS SHAs |
src/fcc/data/personas/research_handoff_liaison.yaml |
RHL persona spec (owner of the research lane) |
src/fcc/data/personas/jv_* (12 personas) |
JV governance + collaboration personas that participate in NEXUS-convened joint ventures |
Cadence alignment table¶
| PI Window | Activity | Owner |
|---|---|---|
| 2026-Q2 | FCC ships seed artifacts under docs/papers/; RHL opens coordination record (this doc) |
FCC (RHL) |
| 2026-Q3 | NEXUS extends quantum-locality paper (methodology + simulation); target venue preprint | NEXUS + FCC (RHL review) |
| 2026-Q3 late | Paper #1 submission to target venue | NEXUS |
| 2026-Q4 | NEXUS extends Zachman-R.I.S.C.E.A.R.+SAFe paper (evaluation + survey) | NEXUS + FCC (RHL review) |
| 2026-Q4 late | Paper #2 submission to target venue | NEXUS |
Open items¶
- Paper #1 (quantum-locality) preprint timing relative to any FCC-INV-002 provisional filing — joint sync between RHL, IHL, and GCA pending
- Paper #2 (Zachman-R.I.S.C.E.A.R.+SAFe) empirical scorecard across 10 constellation projects — NEXUS methodology draft in progress
- Practitioner survey (N ≥ 40) for Paper #2 — survey instrument pending NEXUS IRB review
- Registry drift detection: confirm NEXUS has accepted the v1.3.5.4 vendoring pattern as the canonical mirror protocol
- Joint sync with IHL for every paper that is adjacent to an invention disclosure (currently: Paper #1 ↔ FCC-INV-002 Dual-Bus Architecture)
Peer coordination with IHL¶
RHL holds the research/academic lane; IHL holds the innovation/patent lane. They coordinate when a paper is adjacent to an invention disclosure, when a venue submission would require defensive-publication review by counsel, or when authorship contracts intersect with inventor declarations. For v1.4.3+, Paper #1 (quantum-locality) is adjacent to FCC-INV-002. RHL and IHL sequence the paper preprint relative to any provisional-filing decision, verify defensive-publication posture is recorded consistently in both the Paper #1 manifest and the Patent Claim Matrix, and hold joint sync with GCA for governance enforcement on the combined artifact set.
References¶
- Sibling record (patent lane):
docs/ecosystem/coordination/phoenix-open-science-coordination.md - Sibling record (integration-tests lane):
docs/ecosystem/coordination/orchestra-integration-tests-coordination.md - Landing page:
docs/ecosystem/coordination/README.md - Tri-authority topology:
docs/ecosystem/tri-authority-topology.md - Procedural contract:
docs/governance/patent-delegation-runbook.md - Patent claim matrix (cross-lane awareness):
docs/governance/patent-claim-matrix.md - Ecosystem alignment status:
docs/ecosystem/alignment-status.md - Vendored registries (v1.3.5.4+):
src/fcc/data/ecosystem/port_allocation.yaml,src/fcc/data/ecosystem/ecosystem_projects.yaml - Drift CI:
tests/test_ecosystem_registry_drift.py - Paper #1 seed:
docs/papers/quantum-locality/ - Paper #2 seed:
docs/papers/zachman-riscear-safe/ - RHL persona:
src/fcc/data/personas/research_handoff_liaison.yaml - Related ADRs: see
docs/decisions/for the five architecture decision records relevant to registry vendoring and paper-handoff patterns