Founder edits: Railiance role refined to reliable deployment & operations; Operational Knowledge added as fourth ecosystem pillar. Edits propagated to EcosystemMap and DogfoodPolicy. DEC-2026-001 resolved; workplan task BINKY-WP-0002-T01 closed in file and hub. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
77 lines
2.8 KiB
Markdown
77 lines
2.8 KiB
Markdown
# 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.
|
|
|
|
## Cross-pillar / unassigned assets
|
|
|
|
To classify during cartography: ConfigAtlas, feature-control,
|
|
consistency-frame, HelixForge-style software factory, markitect, personhood,
|
|
foerster_capabilities, the-custodian / state-hub itself (candidate product:
|
|
agentic company cockpit).
|
|
|
|
## Capability entry template
|
|
|
|
```yaml
|
|
capability: <name>
|
|
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
|
|
```
|