Visual System Draft — Version 1.1 — May 2026
Core operating distinction: Fellowship admission grants controlled methodological access. Institutional recognition validates a function within a defined scope. A separate license authorizes real-world use. Enterprise deployment occurs only through a distinct contractual monitoring and governance pathway.

1. Fellowship + Recognition + Fellow License Architecture

This flowchart represents the controlled pathway from candidate application to fellowship participation, institutional recognition, standing management, and, where applicable, a separate case-based license for real-world use of the c-ECO framework.

Flowchart 1 — Controlled Fellowship Entry Layer
Applicant / CandidateProfessional profile + proposed case environment
↓
Case SummaryConcrete asset, operation, exposure, transaction, or governance problem
Professional ProfileExperience, sector relevance, institutional fit
↓
Case Viability ReviewSystemic relevance + signal viability + reversibility exposure
↓
Viable Case?Admission depends on case viability, not credentials alone
NoDeferral / restructure case / non-selection
YesFellowship admission decision
↓
Contractual Adhesion Layer
FPAFellowship Participation Agreement
MAIMethodological Adherence Instrument
CDGAConfidentiality & Data Governance Agreement
CSAMCase-Specific Analytical Mandate
↓
Controlled Methodological Environment
Phase IGuided methodological immersion
Phase IICSAM development + threshold mapping
Phase IIIField / Living Lab integration where applicable
↓
Methodological ReviewValidated function within approved scope?
NoCorrection / conditional status / no recognition
YesInstitutional recognition issued by Foundation
↓
Recognition + Standing Layer
AnalystDiagnostic + threshold interpretation
SeniorContractual translation + supervised case application
ArchitectGovernance design + system integration
ActiveValid within scope
ConditionalCorrective requirements
LapsedExpired / no current standing
Suspended / RevokedIntegrity breach or institutional sanction
↓
Separate License Layer
Real-World Use Requested?Operational, contractual, institutional, or monitoring application
NoRecognition only — no operational license
YesSeparate license review by Foundation
↓
License Approved?Case sensitivity + sector + data + scope review
NoNo deployment authorization
YesCase-based c-ECO license
↓
Licensed ScopeSector + case + duration + standing + methodological version
Lifecycle ControlRenewal / revalidation / suspension / revocation
↓ Unauthorized derivative use may trigger revocation, access suspension, license termination, and legal remedies ↓
Unauthorized Derivative Use ProtectionRevocation, license termination, access suspension, and legal remedies for unauthorized derivative or competing use

2. Exit & Non-Completion Pathways

Fellows may exit the program through multiple pathways. Each pathway has distinct contractual, recognition, and standing consequences.

Flowchart 1A — Fellow Exit Architecture
Enrolled FellowUnder FPA, MAI, CDGA, CSAM
↓
Exit Trigger
DropoutVoluntary withdrawal before completion
IncompleteNon-completion of required phases
ExpelledViolation of FPA, CDGA, or integrity standards
LapsedStanding expired without renewal
↓
No RecognitionDropout / Incomplete / Expelled / Lapsed before recognition
Standing AffectedActive → Conditional / Lapsed / Suspended / Revoked
↓
Post-Exit ObligationsReturn of materials + confidentiality survival + non-circumvention + no derivative use

3. Fellowship Layer Matrix

Layer Function What It Does Not Confer
Admission Entry into controlled methodological environment. No certification, no license, no operational authorization.
Participation Guided analytical work under FPA, MAI, CDGA, and CSAM. No independent use of c-ECO in real-world cases.
Recognition Foundation-issued validation of function within scope. No permanent accreditation or general professional authority.
Standing Current validity status: Active, Conditional, Lapsed, Suspended, Revoked. No expansion beyond the certificate scope.
License Separate authorization for real-world use in a defined case. No unrestricted deployment or sublicensing rights.

4. Fellow → Enterprise Bridge

Licensed fellows may be engaged as analysts, senior reviewers, or architects under enterprise monitoring agreements, subject to separate contractual terms and Foundation authorization.

Flowchart 1B — Licensed Fellow to Enterprise Pipeline
Licensed FellowValid standing + case-based license
↓
Enterprise Engagement RequestCompany/institution requests c-ECO monitoring or governance services
↓
Foundation Authorization?Match fellow expertise + enterprise need + case sensitivity
NoFellow not authorized for this engagement
YesSeparate enterprise service agreement
↓
Enterprise DeploymentFellow operates under Foundation supervision within licensed scope
Foundation OversightQuality control + methodological integrity + reporting

5. Enterprise Contractual Monitoring + Governance Architecture

This flowchart represents the enterprise pathway for companies, institutions, project sponsors, or public-private actors seeking to apply c-ECO in contractual monitoring, systemic risk governance, TFP calibration, and continuous pre-threshold oversight.

Flowchart 2 — Enterprise Deployment and Monitoring Layer
Company / InstitutionEnterprise, project sponsor, public body, investor, operator, or consortium
↓
Institutional BriefingInitial conversation + sector + project context
↓
Initial Systemic AssessmentRisk structure, operational boundaries, decision points
Compatibility ReviewFit with c-ECO pre-threshold governance logic
↓
c-ECO Applicable?Does the project involve monitorable systemic risk?
NoTraditional governance / no c-ECO deployment
YesProceed to scope definition
↓
Project Scope DefinitionAsset, operation, contract, territory, portfolio, or transaction
Signal Viability AssessmentData sources + measurable indicators + monitoring capacity
↓
Signal Viability Adequate?Can TFP be meaningfully computed?
NoRestructure data / redesign case / reject deployment
YesThreshold architecture design
↓
TFP Configuration Layer
PPosition relative to threshold
ΔVVelocity / rate of change
σUncertainty / confidence limits
LrReversibility liquidity
↓
Contractual Monitoring ArchitectureClauses + triggers + data governance + escalation design
↓
Service Tier SelectionStructured Entry / Operational Governance / Institutional Integration
↓
Contractual Implementation Layer
License / Service AgreementScope + fees + monitoring obligations + data rules
Monitoring ProtocolReporting cadence + dashboard + escalation pathways
↓
Continuous TFP MonitoringTrajectory-based classification under current data conditions
↓
Systemic ClassificationGreen / Amber / Red / Black
↓
Governance ResponseReview, escalation, Safe Mode, restoration-first logic, renewal, recalibration

6. Three Enterprise Service Tiers

Tier I

Structured Entry

Initial diagnostic, systemic mapping, signal viability review, preliminary TFP framing, and basic contractual clause integration for small-scale or pilot environments.

Tier II

Operational Governance

TFP calibration, dashboard logic, periodic monitoring, governance review, escalation pathways, contractual triggers, and Safe Mode response planning.

Tier III

Institutional Integration

Portfolio-level integration, multi-contract governance, AI-assisted monitoring, cross-border coordination, continuous recalibration, and institutional implementation.

Pricing: Tier-specific fees may be disclosed only through controlled institutional materials, case-specific proposals, or separate written service agreements. All enterprise engagements require a separate written service agreement and license instrument issued by the Foundation.
Tier Primary Use Typical Components Contractual Form
Tier I — Structured Entry Pilot, initial review, small-scale application. Diagnostic, mapping, clause review, basic monitoring logic. Limited license / pilot service agreement.
Tier II — Operational Governance Mid-scale project, active contract, operational risk monitoring. TFP calibration, dashboard, periodic review, escalation architecture. Monitoring agreement + license + data governance annex.
Tier III — Institutional Integration Enterprise, infrastructure, sovereign, cross-border, high-sensitivity systems. Portfolio governance, multi-contract integration, AI-assisted monitoring, continuous recalibration. Master services + institutional license + monitoring protocol.

7. Systemic Classification Bands & Concrete Actions

Band Trigger Condition Concrete Governance Actions
GREEN Normal execution
routine monitoring 		System within normal operating parameters. No threshold proximity detected. Routine monitoring. Standard reporting cadence. No escalation required. Preventive measures maintained.
AMBER Enhanced monitoring
compressed decision window 		System approaching threshold. Accelerated indicators. Compressed decision window. Enhanced monitoring frequency. Stakeholder notification. Preventive action planning. Contractual review trigger activated.
RED Safe Mode
containment priority 		Threshold proximity critical. Safe Mode conditions met. Containment required. Safe Mode activation. Contractual suspension or modification. Emergency stakeholder assembly. Mediation or arbitration trigger. Regulatory notification where required.
BLACK Restoration-first
irreversibility / emergency logic 		Irreversibility detected or imminent. Emergency logic applies. Restoration-first priority. Restoration-first protocol. Transaction reversal or suspension. Full regulatory notification. Legal remedy activation. Post-event systemic review. Recalibration of all monitoring parameters.

8. Living Lab Integration in Enterprise

Living Labs serve as field validation nodes where enterprise monitoring logic is tested, calibrated, and refined under real-world conditions before broader deployment.

Flowchart 2A — Living Lab as Enterprise Validation Node
Enterprise Tier II/IIIOperational or institutional integration engagement
↓
Living Lab SelectionGeographic + sector + community + data availability match
↓
Field CalibrationTFP parameters tested against local conditions
Community ProtocolFPIC + territorial engagement + local stakeholder alignment
↓
Validation Cycle3–6 months of monitored data collection + methodological adjustment
↓
Validation Successful?Data quality + methodological fit + community acceptance
NoRedesign parameters / change Lab / abort deployment
YesAuthorized for broader enterprise deployment
↓
Scaled DeploymentEnterprise monitoring protocol applied to full operational scope
Continuous Lab FeedbackField data feeds back into TFP recalibration

Operational Traceability Layer

Operating states, artifacts, governance decisions, and exception protocols for Fellows, Enterprise Clients, and Living Labs within the c-ECO system.

State Registry
Happy Path
Applied
Screened
Fellow-Active
Fellow-Alumni
Enterprise-Ready
Enterprise-Active
Pre-Admission Exceptions
Deferred
Rejected
Post-Admission Exceptions
Withdrawn
Suspended
Terminated

States apply differently to Fellows, Enterprise Clients, and Living Labs. See Governance Matrix for entity-specific routing.

State Logic

Participant Status

Each entity exists in a defined operational state. Movement requires a documented activation condition, approving actor, traceable artifact, and archive location.

Gate Criteria

Pass / Hold / Exit

Each transition is governed by a threshold-based gate: accepted, deferred, rejected, withdrawn, suspended, terminated, or escalated to Safe Mode.

Exception Path

Graceful Degradation

When a node fails, the system routes the entity into deferred, withdrawn, suspended, or terminated status. Safe Mode triggers for data breach or methodological conflict.

Traceability rule: each operational node must identify its activation condition, responsible authority, input, process, output, gate, exception route, and archive location.
Artifact Registry
Artifact Activation Point Responsible Authority Gate / Output Archive
Application Form Portal submission Administrative Intake System Initial validation → Review queue Fellowship Portal DB
Screening Report Application validated Coordination Fellowship Eligibility gate → FPA or Rejected Shared Drive / GitHub
FPA Core Agreement Screening passed Legal / Program Administrators Execution → Fellow-Active status Contract Repository
MAI Exhibit A Module 3–4 completion Methodology Lead / Board Threshold ≥ 7.5 → Enterprise-Ready Audit Trail
Enterprise Readiness Report Assessment Fellow-Alumni status + MAI threshold Board c-ECO Board vote → Enterprise-Ready or Deferred Board Minutes Archive
CDGA Exhibit B Enterprise-Ready approved Legal / Compliance Execution → Enterprise-Active Encrypted Vault
LLEP Exhibit C Living Lab activation request Lab Lead / ISM Protocol signed → Lab operational Lab Operations DB
CSAM Exhibit D Case-specific trigger CSAM Lead / Board Mandate issued → Analysis authorized Case Repository
Outcome Record Feedback Enterprise engagement closure Lab Lead / Program Administrators Data captured → Curriculum recalibration Feedback Loop DB
Governance & Exception Matrix
Decision Decision Level Instrument Exception Route
Approve Fellow Fellowship Coordination Screening Report + FPA Rejected / Deferred
Move to Enterprise-Ready Board c-ECO MAI threshold + Readiness Report Fellow-Alumni / Deferred
Activate Enterprise Track Legal + Compliance CDGA + MSA / Service Terms Suspended / Terminated
Activate Living Lab Lab Lead + ISM LLEP Protocol Operational Pause / Lab Reassignment
Authorize Case Analysis CSAM Lead + Board CSAM Mandate Scope Revision / Safe Mode
Financial Non-Compliance Finance + Legal Payment Default Notice Payment Delay → Payment Default → Terminated
Data Breach Compliance + Board Emergency Forensic Audit + CDGA Review Safe Mode → Suspended → Terminated
Methodological Non-Compliance MAI Lead + Lab Lead Corrective Action Plan Re-training → Safe Mode → Suspended
Operational Traceability Layer — Version 1.0 — May 2026