THE SHARED FOUNDATION OF FM WORK

One registry.
Every project.
In sync.

A common language for my developer ecosystem. Define projects, deployments and shared identity once. Build something different with each.

Public configuration Contract v1 FM Work

SMALL FILES. SHARED CONTEXT.

CONFIG ECOSYSTEMJSON

config/global.json

1{2  "version": 1,3  "username": "Fikrimarzuki",4  "domains": {5    "primary": "fikrimarzuki.work"6  }7}

EXCERPT

Shared identity and domains, defined once.

Validated before it travels.Schema checks → semantic checks → consumer build

Define once

Canonical facts live together.
Each application owns its presentation.

Schemas and cross-record checks
keep the registry consistent.

Consumers sync the same JSON
before their own build and deploy.

A MAP FOR THE ECOSYSTEM

Explore shared identity, project models, deployment URLs and collection rules.

Sync configuration at build time and turn canonical facts into application data.

Understand the separate, content-bound approvals for Career and Concepts.