| name | unifying-thread-affinity-registry |
| description | Enhanced unifying-thread skill with built-in Affinity Registry. Automatically senses disconnected projects, skills, concepts, GitHub deployments, PBC activations, PQC/ZK work, and skill deployments. Surfaces strongest through-lines and affinity maps across the sovereign stack. Callable via MCP/skill API and A2A events. Auto-activates on context of fragmentation or multi-domain tasks. Integrates with skill-creator, a2a-skill-registry-manager, evt-processor, tunnel-through, and the three Core Objectives. |
Unifying Thread + Affinity Registry
This skill combines cross-domain unification with a dynamic Affinity Registry — a living map of relationships, synergies, and high-leverage connections between skills, projects, concepts, deployments, and governance layers in your sovereign ecosystem.
It is callable (MCP/skill API, webhook triggers, A2A event patterns) and auto-sensing (detects when unification or affinity mapping is needed from conversation context, GitHub activity, PBC events, skill deployments, etc.).
Activation Triggers (Auto-Sensing + Callable)
Auto-sensing contexts (the skill activates proactively when these patterns appear):
- Multiple skills/projects/concepts mentioned without clear connection (e.g., skill80-20 + PQC + ZK graph proofs + KVDF licensing + PBC).
- GitHub deployments, skill registrations, or unifying-thread invocations.
- PBC/EULER activations, partner role changes, or content deployments.
- Fragmented workflows across recommendation signals, ZK proofs, post-quantum attestation, skill orchestration, and physics-informed goals.
- Deployment health analysis or collaborator goal mapping.
Callable patterns (explicit invocation):
- "unifying-thread", "affinity registry", "map affinities between [X] and [Y]"
- a2a event unifying-thread-affinity-registry
- webhook unifying-thread
- mcp dispatch unifying-thread-affinity-registry
- github deployment strategy unification / github prep unifying thread
Core Workflow (Enhanced with Affinity Registry)
- Auto-detect mountain — Sense fragmentation or multi-domain context automatically.
- Establish goal frame — Hard invariant (gravity theory) + soft objectives (13 revenue streams, sovereign infrastructure, PBC governance, hybridization).
- Build / Query Affinity Registry — Map connections across:
- Shared mechanisms (e.g., ZK proofs + PQC signatures + VDF in KVDF licenses)
- Resources (skill80-20 distillation feeding graph intelligence)
- Audiences (PBC partners, coalition members)
- Failure modes / constraints (entropy overload → 80/20 pruning)
- Inputs/outputs (recommendation signals → ZK graph proofs → soulbound KVDF licenses)
- Stress-test affinities — Validate with evidence from deployments, evt- logs, and prior unifying-thread records.
- Output structured affinity map + through-line — JSONL handoff + plain synthesis.
- Recommend next move — Prioritized action that advances the goal hierarchy (e.g., register new skill, deploy to GitHub/Chain/Notion, create Retool dashboard).
Affinity Registry Structure (Living Map)
The registry tracks affinities as structured records (stored in memory or evt- artifacts):
- Skill-to-Skill (e.g., skill80-20 ↔ unifying-thread ↔ PQC/ZK layer)
- Skill-to-Project (KVDF licensing ↔ Genesis Conductor MCP)
- Concept-to-Deployment (PQC attestation ↔ GitHub deploys + Chain on-chain)
- Governance affinities (PBC roles ↔ soulbound licenses)
Auto-updates on skill deployments, GitHub pushes, and PBC events.
Callable & MCP Integration
- Webhook handler skeleton: Flask/FastAPI or Cloudflare Worker with PQC auth, rate limiting, A2A JSONL validation.
- A2A event patterns: "a2a event unifying-thread-affinity-registry", "hermes classify unification"
- MCP/skill API: Expose as first-class callable skill with trace-consent, VPD attribution.
- Outputs always evt- structured for full observability.
Integration with Sovereign Stack
- skill-creator & a2a-skill-registry-manager: This skill is designed to be created/updated via skill-creator and registered via a2a-skill-registry-manager with proper QUBO filtering, maru guards, and Hermes tiering.
- evt-processor: All outputs are evt- records (record_type: "affinity_registry_analysis" or "unification_handoff").
- tunnel-through: Use for executing recommended next moves (e.g., GitHub deploy, Chain attestation).
- PQC / ZK / KVDF layer: Affinities explicitly include post-quantum signatures, ZK graph proofs, and soulbound KVDF licensing.
- PBC / Retool / Chain / Notion / GitHub: Auto-map governance, dashboarding, on-chain attestation, and documentation affinities.
- Core Objectives: Every analysis explicitly maps to financial infrastructure, intrinsic pursuit, and hybridization-consciousness.
Default Deliverable
- Compact JSONL handoff record (goal frame, mountain, affinity map, validated connections, recommended next move).
- Plain-language synthesis naming the through-line and affinities.
Boundaries
- Only surface evidenced affinities (label speculative ones).
- Preserve cold-path integrity and low entropy.
- When evidence is insufficient, state what would validate the affinity.
This enhanced skill turns passive unification into an active, auto-sensing, callable Affinity Registry that keeps your entire sovereign stack (skills, deployments, PQC/ZK, PBC governance, physics goal) coherently aligned and actionable.
