The operating method: from legitimate demand to independently received value
The 561 Group's operating method turns legitimate demand into independently received value while increasing its ability to do so again. Work is accountable collective activity: an authorized office responds to a real requirement, changes something in the world, establishes what happened, and improves the means available for the next attempt. The method applies to science, engineering, operations, public service, governance and maintenance, and to human and synthetic workers through the offices they actually hold.
What is the first rule of the method?
Improve the carrier first. Every prompt, session, office shift and delegated work cycle begins by improving or qualifying the method that will carry the requested work, and only then performs the domain work through that improved method. This is an ordering constraint, not a closing reflection. A chat explanation, a retrospective apology or a one-off manual repair does not count as changing the operative instruction, skill, program, installation or runbook.
Why put method before work? Because in a firm of agents the same mistake is cheap to repeat. If a correction lives in a conversation, the next session will make the mistake again. If it lives in a rule, a skill, a test or a deployed mechanism, a fresh worker will follow it. The Group's phrase is that reusable capability, not a promise to remember, is the durable yield of an improvement.
What is the debrief, and why is it mandatory?
Every work turn has a debrief before new execution and after receiving. At entry, inspect the previous attempt's actual source, runtime and customer state and its stated goal; name what failed, was unnecessarily duplicated, remained merely proposed, or was claimed without independent receiving. Ask what smaller or more capable method would have prevented it, then change the owning skill, runbook, test, executable or consumer path before doing more domain work. During execution, compare the intervention with the observed effect. At closure, record a short evidence-bound comparison: the intended receiver result, the actual received result and revision, the surprise, and the change to the method that follows.
The rule has a sharp edge. If the debrief changed only chat text or a proposed edit, it is not complete. If a needed step cannot be performed, the worker executes another lawful useful unit instead of ending with a catalog of what remains.
How does work begin?
With a receiver and an outcome. Identify the principal, the receiving party, the outcome sought, the standing duty and authority for the work, and the evidence that would establish satisfaction. An internal receiver is a real link in the chain, but the ultimate customer's or public's outcome stays visible beyond that link. Ideas and questions enter inquiry; authorized requirements enter work; recorded decisions govern action.
For new software capability the order is non-substitutable: requirements, specification, architecture, design, fabrication, followed by integration, operation and independent receiving. One document, approval or hash cannot discharge more than one distinct admission. A small product reduces scope; it does not reduce the number of admissions.
How is work given form?
The method keeps a containment order called the work spine.
| Level | Meaning |
|---|---|
| Endeavor | A sustained aim across attempts; its history accumulates capability even when an attempt misses |
| Campaign | A coordinated, time-bounded push with an objective and horizon |
| Project | A scoped body of work with outputs and responsible offices |
| Plan | A partial order of tasks, distinguishing dependencies from concurrency |
| Task | A bounded attempt against a standing duty, with an executable goal check |
| Work-item | The atomic unit within a task; its standing is read from recorded actions |
Achieved, failed or abandoned is read from the recorded attempt and its goal, not declared as a status. Maintenance, refusal, governance, repair and research are work even before anyone has packaged them as tasks.
How does the method relate to MAPE-K?
After the carrier-first step, every operating turn follows a recursive circuit: monitor, analyze, plan, execute, verify, improve. The circuit adds verify and improve to the textbook four, and it never postpones improvement until after the requested work. That is MAPE-K (how to run a company as a MAPE-K loop) with the knowledge stage made active: the Knowledge in the loop is what the improve step writes to.
What counts as received?
For a service, the method distinguishes ten states that sloppy reporting merges: authorized requirement, source change, integrated source, successful checks, release, deployed runtime, executed effect, provider delivery, independent assay and receiver acceptance. Each has its own evidence. A handoff, self-reported completion or internal approval is useful information; only actual receiving settles whether the sought outcome was delivered. Economic results similarly distinguish activity and transfers from attributable customer settlement.
The shorter form is the ladder in how to prove a service reached someone.
How does the Group decide what work is worth doing?
By attainable after-cost contribution, usable capability, reusable leverage and the option to enter an emerging market early, measured against the Group's actual capital and capacity. The method states that a market's youth, one provider's cumulative revenue, an uncertain present buyer count, or a small dollar figure by a large incumbent's standards is not negative evidence about the economics of one Group-sized agent operation. An agent may profitably perform thousands of lawful microtasks that would be irrational for a person to do individually. The priority is to make those agent-usable operations cheap, accessible, repeatable and sellable. A companion rule says to reason first toward the cheapest lawful productive action and to refuse only on evidenced loss, unqualified rights, actual capacity limits or a better opportunity.
The method pairs this with a refusal discipline: refuse model-imagined demand before engineering it. Demand has to come from a real receiver.
How is state kept legible?
Work declarations and witnessed acts are content-addressed, append-only statements. Corrections add new evidence; projections of active work, milestones and books are reproducible readings. The continuation test is whether a fresh worker can find the next admissible action from durable records without the original conversation.
The producing office saves substantive work in its owning organization's repository or authorized store during the work, before reporting delivery in chat. Chat messages, sandbox files and staging areas are working material, not completed delivery. This is why an unmerged branch is not a deliverable.
What does the method say about publishing?
Public writing belongs to the service's outcome. For each audience-facing resource, establish the intended reader, one concrete question it answers, its subject-owning office, canonical source identity, admissible evidence, editorial and reuse rights, the next action offered and a way to observe whether it was received. Publish one accepted primary explanation for a subject; homepages, feeds and social posts project that same identity and point back to it. Do not invent dates, deliveries, followers or readiness. Proposed copy, accepted copy, built artifacts, provider release, outside readback, distributed posts and audience response are different states. We follow this on this site: each article here is the primary Coesite explanation, and the research it draws on stays with Lenticule Science.
What are the limits?
The method is written down and governs how offices are asked to work. How faithfully any given session followed it on any given day is a matter for the dated record. The method is also not a claim that the Group is large or profitable; no figures are given or implied here.
Where to go next
Can an AI agent hold an office? · Deterministic tools before model tokens · First contact is one-shot · the 561 Group · Services