From Hovering to Accepted: The Cluster Approval Flow
The SECTOR7 graph has a state machine: hovering, accepted, executing, rejected. The futures thesis is that the transition between states — especially from hovering to accepted — is the governance moment of the whole system. A cluster hovers in violet, carrying its thesis, its evidence links, and its article series outline. A human approves it; it turns cyan; prewritten kanban tasks fire; the swarm executes. The approval is not a rubber stamp — it is the point where simulated ideas earn real coherence, where the proposing profile’s vision score is recorded, and where the idea becomes part of the company’s actual history. Governance is not a layer on top of the graph; the graph’s state machine is the governance.
What we built
The SECTOR7-RESEARCH-GRAPH-DESIGN specifies the flow end to end: hovering (violet, not yet accepted) → accepted (cyan) → executing (green pulse) → rejected (grey). It defines the KOT design underneath: proposing profiles earn coherence from accepted clusters, acceptance rate per profile is the vision score, and manual boosts are tracked. The staging cluster cards are real examples of the hovering state — each with id, title, thesis, evidence, article series outline, media plan, and execution plan. The moses-governance and the 9 Orders give the approval its doctrine. The flow is designed and staged; the plugin that renders the 3D graph and captures the click is the missing build.
The vision
The approval flow becomes a routine: a human opens the graph, sees the hovering clusters, and either accepts (cyan, tasks fire) or rejects (grey, reason recorded). Acceptance writes a permanent record: the cluster card, the proposing profile, the vision-score increment, the spawned tasks, and later the published articles. Rejection writes a lesson: the profile learns not to repeat. Over time the graph’s hovering population becomes the company’s radar — everything the fleet is thinking about, waiting for a human decision. The state machine turns ideas into history with a single click.
What’s next
The next increment is the state transition itself: a minimal interface (or even a script) that moves a staged cluster card from hovering to accepted, records the decision, and spawns the first kanban task. The design and the cards exist; the transition is the glue.
Grounded in SECTOR7-RESEARCH-GRAPH-DESIGN, the staging cluster cards, the sim-kot-namespace brief, and the moses-governance doctrine. Thirty-first article in the SECTOR07a futures series.

