Intelligence should expand what people can build together.
Retain outcomes, finite resources and the decisions reserved elsewhere.
Actual agreed scope/resources and reserved decisions.
Actual scoped decision making the revised mandate effective.
Retain outcomes, finite resources and the decisions reserved elsewhere.
Agreed objective and acceptance basis.
Active mandate, pending proposal and prior versions remain distinct.
A pending proposal neither expands nor disables unrelated work under the current effective mandate.
Make changed dependencies and relevant lessons inspectable.
Actual dependency change and evidence.
Attributed experience available to future deliberation.
Make changed dependencies and relevant lessons inspectable.
Independent changed dependency and its source.
Decisions, observations and useful failures.
Changed dependencies and lessons retain their actual source.
Compare proposals, consequences and objections from affected teams.
Relevant changed evidence and consequences.
Explicit expanded-scope proposal with resource/consequence basis.
Objection and bounded alternative.
Current mandate and the agreed decision-right holder.
Compare proposals, consequences and objections from affected teams.
Proposed expanded scope and bounded alternative.
Unresolved objections and the existing decision right.
Unresolved disagreement remains visible until the existing decision holder supplies a decision.
Let teams perform inspectable work within the effective mandate.
Effective bounded mandate and acceptance criteria.
Specific finding requiring correction under the same work context.
Let teams perform inspectable work within the effective mandate.
Independent responsibilities and bounded resource basis.
Actual team artifacts and incomplete work remain separate.
Teams work within the selected effective mandate and resource basis.
Compare identified work against the agreed criteria and return specific findings.
Identified team artifacts and actual evidence.
Original agreed criteria and effective scope.
Compare identified work against the agreed criteria and return specific findings.
Evidence and acceptance criteria.
Unresolved finding tied to the same work item.
Findings refer to the identified work and agreed criteria.
Make results, failures and open questions usable by another team.
Reviewed result, useful failures and unresolved questions.
Make results, failures and open questions usable by another team.
Accepted artifact, evidence and responsibility.
Useful failures, unresolved questions and next-team context.
Handover carries unresolved questions and responsibility; it does not transfer governing power by itself.
Actual agreed scope/resources and reserved decisions.
Actual scoped decision making the revised mandate effective.
Retain outcomes, finite resources and the decisions reserved elsewhere.
Agreed objective and acceptance basis.
Active mandate, pending proposal and prior versions remain distinct.
A pending proposal neither expands nor disables unrelated work under the current effective mandate.
Actual dependency change and evidence.
Attributed experience available to future deliberation.
Make changed dependencies and relevant lessons inspectable.
Independent changed dependency and its source.
Decisions, observations and useful failures.
Changed dependencies and lessons retain their actual source.
Relevant changed evidence and consequences.
Explicit expanded-scope proposal with resource/consequence basis.
Objection and bounded alternative.
Current mandate and the agreed decision-right holder.
Compare proposals, consequences and objections from affected teams.
Proposed expanded scope and bounded alternative.
Unresolved objections and the existing decision right.
Unresolved disagreement remains visible until the existing decision holder supplies a decision.
Effective bounded mandate and acceptance criteria.
Specific finding requiring correction under the same work context.
Let teams perform inspectable work within the effective mandate.
Independent responsibilities and bounded resource basis.
Actual team artifacts and incomplete work remain separate.
Teams work within the selected effective mandate and resource basis.
Identified team artifacts and actual evidence.
Original agreed criteria and effective scope.
Compare identified work against the agreed criteria and return specific findings.
Evidence and acceptance criteria.
Unresolved finding tied to the same work item.
Findings refer to the identified work and agreed criteria.
Reviewed result, useful failures and unresolved questions.
Make results, failures and open questions usable by another team.
Accepted artifact, evidence and responsibility.
Useful failures, unresolved questions and next-team context.
Handover carries unresolved questions and responsibility; it does not transfer governing power by itself.
An illustrative organization of shared purpose, challenge, bounded delivery and useful handover; software is optional.
Additional mechanisms are described in the technical reference.
We are building a lab where specialized people and systems can work toward a shared purpose while retaining their independence.
Knowledge should travel. Responsibility should be clear. A useful system should make it easier for the next person to build on what came before.
Our research extends to the organization itself: how a team remembers, notices what matters, makes decisions and hands over work. People determine purpose and authority; software can make their coordination more inspectable.
Research, engineering, design and the way we organize belong in the same conversation. Meet the people building Naevum.
Collectively, members of our team have worked with these organizations.
We call these functions organizational organs.
Notice changes and retain the evidence, decisions and lessons that make them intelligible.
Create places to examine alternatives, disagree and assign a bounded mandate.
Make work visible, judge the result and preserve a path to correction.
Turn useful experience into shared knowledge that can survive a handover.
A bounded team receives a purpose, the authority to carry it out and a way to account for the result.
Define the outcome, resources and decisions that stay with others.
Retain decisions, evidence and unresolved questions as the work proceeds.
Share the accepted result and useful failures so another team can continue from them.
We want to share adaptable models for horizontal organization and support creation and adoption programs.
Understand responsibilities, knowledge flows and the decisions people repeatedly struggle to make.
Choose organs and mandates appropriate to the people, work and legal setting.
Observe the result, revise the model and document what another organization could reuse.
Proposed adoption-pilot example: a delivery team asks to expand a mandate because a shared dependency has changed.
The initiating team records the proposed scope, resources and consequence. The team responsible for the affected dependency can challenge the assumptions and suggest a bounded alternative.
The person or group holding the agreed decision right resolves the scoped question. The revised mandate becomes effective through that recorded decision; the earlier version and unresolved objections remain inspectable.
This is a worked program proposal. Each organization agrees its own decision rights, stewardship and conflict-resolution process in its actual legal and operating setting.
The mission is to develop and share adaptable models. An organization’s people, work and legal setting determine how a model should be designed and tested.
People commissioning intelligent systems, researchers, builders and organizations interested in a practical program for horizontal coordination.
Sensing and memory. Notice changes and retain the evidence, decisions and lessons that make them intelligible.
Deliberation and responsibility. Create places to examine alternatives, disagree and assign a bounded mandate.
Delivery and review. Make work visible, judge the result and preserve a path to correction.
Learning and continuity. Turn useful experience into shared knowledge that can survive a handover.
Agree the responsibility. Define the outcome, resources and decisions that stay with others.
Make the work inspectable. Retain decisions, evidence and unresolved questions as the work proceeds.
Return knowledge. Share the accepted result and useful failures so another team can continue from them.
What could these mechanisms make possible for you?
Build with Naevum
