Compare commits
2 commits
08e360a35d
...
5b1a4f62f5
| Author | SHA1 | Date | |
|---|---|---|---|
| 5b1a4f62f5 | |||
| 49d9ce2569 |
6 changed files with 54 additions and 33 deletions
|
|
@ -22,25 +22,23 @@ fallback_if_no_response: ""
|
|||
|
||||
## Open decisions
|
||||
|
||||
*(none)*
|
||||
|
||||
## Resolved decisions
|
||||
|
||||
### DEC-2026-001 — Ratify company canon v0
|
||||
|
||||
```yaml
|
||||
id: DEC-2026-001
|
||||
title: "Ratify company canon v0 (INTENT, AutonomyPolicy, and companion docs)"
|
||||
lane: red
|
||||
status: prepared
|
||||
created_at: "2026-07-16"
|
||||
needed_by: "2026-07-23"
|
||||
attention_cost: "30 min"
|
||||
agent_recommendation: "Review INTENT.md and AutonomyPolicy.md closely (they govern everything else); skim the rest. Approve with edits."
|
||||
status: resolved
|
||||
outcome: approved with edits
|
||||
resolved_at: "2026-07-16"
|
||||
resolved_by: Bernd
|
||||
edits: "Railiance role refined to reliable deployment & operations (code → SaaS ecosystems and products); Operational Knowledge added as fourth ecosystem pillar (value from experience). Edits propagated to EcosystemMap.md and DogfoodPolicy.md."
|
||||
evidence:
|
||||
- INTENT.md
|
||||
- INTENT.md (v1.0)
|
||||
- AutonomyPolicy.md
|
||||
- history/260715-InitialExploration.md
|
||||
options: [approve, reject, revise, defer]
|
||||
fallback_if_no_response: "Canon stays draft; agents operate under conservative lane defaults; no external-facing artifacts produced."
|
||||
consequence: "Canon v1.0 in force; AutonomyPolicy lanes active; Green/Blue work may proceed unattended."
|
||||
```
|
||||
|
||||
## Resolved decisions
|
||||
|
||||
*(append resolved items here: id, title, outcome, date, evidence)*
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ dogfood_case: ""
|
|||
date: ""
|
||||
pain: ""
|
||||
capability_used: ""
|
||||
pillar: coulomb | net_kingdom | railiance | cross
|
||||
pillar: coulomb | net_kingdom | railiance | operational_knowledge | cross
|
||||
before: ""
|
||||
after: ""
|
||||
effort: ""
|
||||
|
|
|
|||
|
|
@ -26,9 +26,9 @@ architecture.
|
|||
Known assets (to verify/expand): OpsBridge, Keycape, OpenBao patterns, PECS,
|
||||
identity-canon, user-engine.
|
||||
|
||||
### Railiance — reliable execution and coordination layer
|
||||
> Coordinates reliable workflows, deliveries, evidence chains, and operational
|
||||
> commitments.
|
||||
### 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.
|
||||
|
|
@ -36,6 +36,16 @@ 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,
|
||||
|
|
@ -47,7 +57,7 @@ agentic company cockpit).
|
|||
|
||||
```yaml
|
||||
capability: <name>
|
||||
pillar: coulomb | net_kingdom | railiance | cross
|
||||
pillar: coulomb | net_kingdom | railiance | operational_knowledge | cross
|
||||
repos: []
|
||||
maturity: idea | prototype | internal_use | productizable | product
|
||||
dogfood_status: not_used | in_use | proven
|
||||
|
|
@ -56,11 +66,12 @@ owner: bernd
|
|||
notes: ""
|
||||
```
|
||||
|
||||
## Triad summary
|
||||
## Pillar summary
|
||||
|
||||
```text
|
||||
Coulomb → discover and shape capability
|
||||
Net Kingdom → secure and govern capability
|
||||
Railiance → coordinate and deliver capability
|
||||
Binky / OK → sell, operate, and prove capability
|
||||
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
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# INTENT
|
||||
|
||||
> Status: **draft v0.1** — 2026-07-16. Owner: Bernd Worsch. To be revised as the company canon grows.
|
||||
> Status: **v1.0 — ratified 2026-07-16** (DEC-2026-001, approved with edits). Owner: Bernd Worsch. To be revised as the company canon grows.
|
||||
|
||||
## Why this company exists
|
||||
|
||||
|
|
@ -32,7 +32,8 @@ The ecosystem pillars and their roles:
|
|||
| --- | --- |
|
||||
| **Coulomb** | Discover, cluster, mature, and package reusable capabilities |
|
||||
| **Net Kingdom** | Identity, access, security, governance — make capability governable |
|
||||
| **Railiance** | Reliable coordination and delivery — turn intentions into fulfilled commitments |
|
||||
| **Railiance** | Reliable deployment and operations — turn code into saas ecosystems and products |
|
||||
| **Operational Knowledge** | Value from experience — drive your business based on what you know |
|
||||
|
||||
## The core loop: the OK Flywheel
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ owner: codex
|
|||
topic_slug: custodian
|
||||
created: "2026-07-16"
|
||||
updated: "2026-07-16"
|
||||
state_hub_workstream_id: "6342819a-0567-4922-8a19-fc9ed68ad6b8"
|
||||
---
|
||||
|
||||
# Bootstrap State Hub integration
|
||||
|
|
@ -21,6 +22,7 @@ binky-control is the company control plane ("company brain") for Binky Hedgehog
|
|||
id: BINKY-WP-0001-T01
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "f348200e-71dc-4188-bab9-bd3699c8cb07"
|
||||
```
|
||||
|
||||
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
|
||||
|
|
@ -32,6 +34,7 @@ Replace generated placeholders with repo-specific facts where needed.
|
|||
id: BINKY-WP-0001-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "26d0b9ff-a75f-4474-b2e5-990eefaeac3b"
|
||||
```
|
||||
|
||||
Identify the repo's install, test, lint, build, and run commands. Add or refine
|
||||
|
|
@ -44,6 +47,7 @@ changes confidently.
|
|||
id: BINKY-WP-0001-T03
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "30562538-d5e8-4355-a422-6da1df2d35c2"
|
||||
```
|
||||
|
||||
Create the first implementation workplan for the repository's most important
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
---
|
||||
id: BNKY-WP-0001
|
||||
id: BINKY-WP-0002
|
||||
title: "Binky / OK Operating Kernel Bootstrap"
|
||||
status: active
|
||||
state_hub_workstream_id: "5c6addae-2759-4212-94dc-d87c47318528"
|
||||
---
|
||||
|
||||
Make Binky Hedgehog GmbH practically operable and strategically aimed at
|
||||
|
|
@ -16,9 +17,10 @@ Review and approve/revise INTENT.md, AutonomyPolicy.md, and companion docs
|
|||
(DEC-2026-001 in DecisionQueue.md). Red lane — founder only.
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T01
|
||||
status: todo
|
||||
id: BINKY-WP-0002-T01
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "80854b7d-0d0e-4c1d-be66-34d2df08955b"
|
||||
```
|
||||
|
||||
## Task: Run Binky Operational Knowledge Audit v0
|
||||
|
|
@ -30,9 +32,10 @@ RiskRegister.md, OfficeHourQueue.md, and becomes the reusable audit template.
|
|||
Green/Blue preparation; findings needing external action go to queues.
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T02
|
||||
id: BINKY-WP-0002-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "f8dce253-a2a2-4a9f-b5ee-341a98e2cec0"
|
||||
```
|
||||
|
||||
## Task: Populate Ecosystem Map via repo cartography
|
||||
|
|
@ -42,9 +45,10 @@ cross, using the capability entry template in EcosystemMap.md. Record maturity
|
|||
and product candidates. Green lane.
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T03
|
||||
id: BINKY-WP-0002-T03
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "6df35c39-373b-406c-8f70-ec9ebcf2905a"
|
||||
```
|
||||
|
||||
## Task: Draft flagship offer — Operational Knowledge Audit
|
||||
|
|
@ -54,9 +58,10 @@ offer in OfferCatalog.md: target segment, promise, deliverables, price
|
|||
hypothesis. Drafting is Green; publishing is Yellow (decision package).
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T04
|
||||
id: BINKY-WP-0002-T04
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "5492bebf-3f54-48a1-8853-ba1252d3926c"
|
||||
```
|
||||
|
||||
## Task: Establish operating rhythm (daily brief + queue hygiene)
|
||||
|
|
@ -66,9 +71,10 @@ best next hour), keep DecisionQueue and OfficeHourQueue current, and seed the
|
|||
Autopilot Work Queue with evergreen Green/Blue work. Blue lane.
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T05
|
||||
id: BINKY-WP-0002-T05
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "98683baa-c7b0-4553-9526-c29841f28d85"
|
||||
```
|
||||
|
||||
## Task: Prepare first Office-Hour Command Day runbook
|
||||
|
|
@ -77,7 +83,8 @@ From audit findings, batch all Orange-lane items (accountant, bank, registry)
|
|||
into a prepared runbook per the OfficeHourQueue.md template. Green preparation.
|
||||
|
||||
```task
|
||||
id: BNKY-WP-0001-T06
|
||||
id: BINKY-WP-0002-T06
|
||||
status: todo
|
||||
priority: low
|
||||
state_hub_task_id: "b9dab91b-2695-4882-837a-89459cd75961"
|
||||
```
|
||||
Loading…
Add table
Add a link
Reference in a new issue