# Ecosystem Map > Status: draft v0.1 — 2026-07-16. Skeleton; to be populated by repo/capability > cartography (see workplan). Ecosystem ≠ company: the ecosystem generates and > matures capabilities; the company commercializes and consumes them. ## Pillars ### Coulomb — capability formation surface > Discovers, clusters, matures, and packages reusable capabilities. Commercial angles: capability registry, reuse marketplace, product ideation surface, repo/product intelligence, adaptive pricing experiments, membership/community layer. Known assets (to verify/expand): reuse-surface, adaptive-pricing, Coulomb membership concepts. ### Net Kingdom — sovereign secure operating substrate > Provides identity, access, security, governance, and operational sovereignty > for agentic and human systems. Commercial angles: IAM/security stack, controlled agent access, audit/security architecture. Known assets (to verify/expand): OpsBridge, Keycape, OpenBao patterns, PECS, identity-canon, user-engine. ### Railiance — reliable deployment and operations layer > Turns code into SaaS ecosystems and products: reliable deployment, > operations, workflows, and operational commitments. Commercial angles: coordination products, evidence-backed communications, delivery/result tracking, workflow reliability. Known assets (to verify/expand): coordination-engine, email-connect, citation-evidence. ### Operational Knowledge — value from experience > Drives the business based on what it knows: turning operational experience > into structured, governed, executable knowledge. Commercial angles: operational knowledge audits, evidence-backed decision ledgers, capability maturity snapshots, agentic company cockpit. Known assets (to verify/expand): citation-evidence, consistency-frame, the-custodian / state-hub patterns, this repo's canon-and-queues model. ## Cartography v0 — 2026-07-16 (BINKY-WP-0002-T03) 85 git repos on the workstation, classified by name and known-asset context at capability-cluster granularity. Bulk migration touched nearly everything on 2026-07-08, so only later commit dates signal genuine current activity (active: railiance-platform/infra/hosts/apps/cluster/bootstrap, ops-warden, binky-control, activity-core, unattended-progress-company, state-hub, the-custodian, reuse-surface, issue-core, hub-core, core-hub, shard-wiki, email-connect, secrets-engine, ops-hub, and the citation/evidence cluster). Maturity values are **unverified estimates** — refine per capability when a repo is next touched. ```yaml capability: capability-reuse-surface pillar: coulomb repos: [reuse-surface, open-reuse, coulomb-loop, repo-scoping, repo-seed] maturity: prototype dogfood_status: in_use product_candidates: [capability registry, reuse marketplace] owner: bernd notes: "reuse-surface actively developed (2026-07-12)" ``` ```yaml capability: adaptive-pricing pillar: coulomb repos: [adaptive-pricing, infospace-bench] maturity: idea dogfood_status: not_used product_candidates: [pricing experiments for subscription platform] owner: bernd notes: "" ``` ```yaml capability: identity-and-access pillar: net_kingdom repos: [net-kingdom, key-cape, flex-auth, identity-canon, user-engine, secrets-engine] maturity: internal_use dogfood_status: in_use product_candidates: [IAM/security stack, controlled agent access] owner: bernd notes: "flex-auth deployed on CoulombCore (bridge tunnel exists); secrets-engine active 2026-07-09" ``` ```yaml capability: ops-sovereignty pillar: net_kingdom repos: [ops-bridge, ops-warden, sand-boxer, disaster-control] maturity: internal_use dogfood_status: proven product_candidates: [tunnel/ops lifecycle tooling, sandboxed agent execution] owner: bernd notes: "ops-bridge + ops-warden run daily on the workstation fleet" ``` ```yaml capability: railiance-platform pillar: railiance repos: [railiance-platform, railiance-infra, railiance-hosts, railiance-apps, railiance-cluster, railiance-bootstrap, railiance-fabric, railiance-forge, railiance-enablement, ihp-railiance-probe] maturity: internal_use dogfood_status: in_use product_candidates: [code-to-SaaS deployment platform, managed operations] owner: bernd notes: "Most active cluster in the portfolio (commits through 2026-07-16); hosts the forgejo remote" ``` ```yaml capability: coordination-and-comms pillar: railiance repos: [coordination-engine, email-connect, llm-connect, tele-mcp] maturity: prototype dogfood_status: in_use product_candidates: [coordination products, evidence-backed communications] owner: bernd notes: "email-connect active 2026-07-10" ``` ```yaml capability: evidence-and-citation pillar: operational_knowledge repos: [citation-engine, citation-evidence, citation-work, evidence-anchor, evidence-binder, evidence-source, audit-core] maturity: prototype dogfood_status: in_use product_candidates: [evidence-backed decision ledgers, audit tooling] owner: bernd notes: "Whole cluster touched 2026-07-09 — coherent build-out under way; audit-core is the natural home for the OK Audit template" ``` ```yaml capability: agentic-company-cockpit pillar: operational_knowledge repos: [the-custodian, state-hub, binky-control, tegwick-control, whynot-control, unattended-progress-company, activity-core, issue-core, kaizen-agentic, ralph-workplan, phase-memory, vantage-point, guide-board] maturity: internal_use dogfood_status: proven product_candidates: [agentic company cockpit, operational knowledge audits] owner: bernd notes: "The canon-and-queues model this repo runs on; strongest dogfood evidence in the portfolio" ``` ```yaml capability: platform-hubs pillar: cross repos: [core-hub, hub-core, ops-hub, fin-hub, domain-tree, config-atlas, feature-control, artifact-store, agent-tools, agentic-resources] maturity: prototype dogfood_status: in_use product_candidates: [] owner: bernd notes: "Shared substrate; classify per-hub when productization nears. core-hub/hub-core pair active 2026-07-11 — likely rename/split in progress" ``` ```yaml capability: markitect-authoring pillar: cross repos: [markitect-main, markitect-tool, markitect-filter, markitect-quarkdown, marki-docx] maturity: prototype dogfood_status: not_used product_candidates: [document/authoring pipeline] owner: bernd notes: "Own custodian domain (markitect); relation to company offers undecided" ``` ```yaml capability: software-factory pillar: cross repos: [helix-forge, glas-harness, polycode-sim, testdrive-jsui, kontextual-engine] maturity: idea dogfood_status: not_used product_candidates: [software factory patterns] owner: bernd notes: "" ``` ```yaml capability: knowledge-and-content pillar: cross repos: [shard-wiki, training-database, info-tech-canon, timeline-svg, snuggles-inventor, can-you-assist, wise-validator, whynot-design, guide-board] maturity: idea dogfood_status: not_used product_candidates: [] owner: bernd notes: "shard-wiki active 2026-07-10" ``` ### Out of scope for the company map Personal/employer/one-off: binect-chrome, binect-js (employer Binect), direkt-vermittlung-de, vergabe-teilnahme (procurement paperwork, active), human-resources, python-snake, open-cmis-tck, plus non-repo folders (0privat, 1binect, 2binky, 3coulomb, bin, go, workenv, terminals, vault). **IP note:** everything above sits in the founder's home directory — GmbH vs. private ownership per capability is exactly RISK-002; the self-billed Eigenentwicklung invoices should be mapped to capabilities as IP evidence. ## Capability entry template ```yaml capability: pillar: coulomb | net_kingdom | railiance | operational_knowledge | cross repos: [] maturity: idea | prototype | internal_use | productizable | product dogfood_status: not_used | in_use | proven product_candidates: [] owner: bernd notes: "" ``` ## Pillar summary ```text Coulomb → discover and shape capability Net Kingdom → secure and govern capability Railiance → deploy and operate capability (code → SaaS products) Operational Knowledge → learn from experience and drive the business on it Binky / OK (company) → sell, operate, and prove capability ```