fpf-local-first-unification-naming-protocol

Mint bounded-context Name Cards using the F.18 Local-First Unification Naming Protocol.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill fpf-local-first-unification-naming-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fpf-local-first-unification-naming-protocol
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/design/fpf-local-first-unification-naming-protocol
Command: npx skills add https://github.com/venikman/fpf-foundry --skill fpf-local-first-unification-naming-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mint bounded-context Name Cards using FPF Local‑First Unification Naming Protocol to prevent cross-context naming collisions and to preserve local meaning while enabling safe cross-context references.

Core Features & Use Cases

  • Anchors names to a Home Context and edition, reducing global name collisions.
  • Requires dual label surfaces (Unified Tech and Plain) and explicit Concept‑Set linkage for auditability.
  • Enables Bridges with loss/fit notes for cross-context integration and maintains lifecycle history for auditable evolution.

Quick Start

Mint a new local term by applying the protocol within your current bounded context. For example: mint-name --context Healthcare --id patient-care --label "Patient Care" --purpose "Clinical workflow optimization".

Frequently Asked Questions about fpf-local-first-unification-naming-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent naming collisions across bounded contexts?

Mint bounded-context Name Cards using the Local-First Unification Naming Protocol to prevent naming collisions. This anchors names to a Home Context and edition, preserving local meaning while enabling safe cross-context references.

What is the Local-First Unification Naming Protocol?

The Local-First Unification Naming Protocol is a method to mint bounded-context Name Cards. It enforces MDS, Purpose, Sense anchoring, and lifecycle events to anchor local meaning and enable safe cross-context Bridges.

How do I mint a local term within a bounded context?

To mint a local term within a bounded context, apply the protocol with your context, ID, label, and purpose. This generates a Name Card with Unified Tech and Plain labels linked to a Concept-Set and registered in the Unified Term Sheet.

Does this protocol support cross-context integration with Bridges?

Yes, this protocol supports cross-context integration by enabling Bridges with loss and fit notes. It maintains lifecycle history for auditable evolution and applies Bridge travel rules for safe external references.

When do I need explicit Concept-Set linkage for naming?

You need explicit Concept-Set linkage for naming when anchoring sense within a bounded context. It provides required auditability alongside dual Unified Tech and Plain label surfaces to maintain stable, auditable naming.