Collaboration And Versioning Policy

Version: v1.1 Status: Locked Owners: FMIE / Foundation / Cortex / Frontend Last Updated: 2026-03-25 Change Type: additive Migration Required: no Depends On: none

Purpose

Define how the three-way session shares specs, updates contracts, and publishes handoffs without version drift.

Repository Model

• One canonical spec repo: /mnt/Storage-1/worktrees/Foundation-V2/Colab
• One shared source of truth for contracts and architecture
• Public HTML is a published view, not the authoritative source

Folder Model

• specs/shared/: cross-boundary contracts
• specs/fmie/: FMIE-owned specs
• specs/foundation/: Foundation-owned specs
• specs/cortex/: Cortex-owned specs
• specs/frontend/: Triton Front-end-owned specs
• specs/handoffs/: sprint and consolidated handoffs

Implementation Ownership

• Codex session: C++ and FMIE-native/runtime implementation
• Cortex session: Python modules and Python service work
• Triton Front-end session: Swift and front-end implementation
• Shared specs can be edited here before language-specific implementation handoff

Document Classes

Each major feature should use at most three docs: - vision - spec - handoff

Versioning

• v0.x: exploratory
• v1.0: contract locked
• v1.x: backward-compatible clarification or additive change
• v2.0: breaking change

Required Header Fields

• Version
• Status
• Owners
• Last Updated
• Change Type
• Migration Required
• Depends On
• Supersedes
• Superseded By

Status Meanings

• Draft: under active design
• Review: ready for cross-layer review
• Locked: contract agreed
• Implemented: materially shipped
• Deprecated: replaced but retained for history

Review Rules

Shared specs require review from: - FMIE - Foundation - Frontend - Cortex if observability, autonomy, or governance is affected

Sprint Discipline

After every sprint: 1. update canonical spec if contract changed 2. update consolidated handoff 3. publish HTML 4. record done / partial / open

Non-Negotiable Rule

No feature is considered real until it has: - a canonical spec - an owner - a contract or schema - a version - a handoff status

Change Log

• v1.1: added implementation-language ownership for the three-way session
• v1.0: initial locked policy