Conduir / Role Fabric
Work custody, role execution, scheduling, memory adapters and governance boundaries.
Inside the ideas
Explore the responsibilities, information flows and design choices behind the work. Each guide connects an idea to a concrete example, its current scope and the questions still to resolve.
Explore the responsibilities, information flows and design choices in each system, then open the retained source views where more detail is useful.
Original source reviews and alternative context, container and component views remain available for deeper reading. Each retains its own date, scope and interpretation.
Work custody, role execution, scheduling, memory adapters and governance boundaries.
All memory representations, retrieval, provenance, memory care and current source limits.
Graph-based software understanding, composition, mathematical analysis and optional learning paths.
Original architecture records · All 18 current / C3 comparisons · Explore the complete research suite · Explore DocuMind
Architectural programme
Conduir is a programme of cooperating capabilities. Context, coordination, action, review and governance have distinct responsibilities. The architecture asks how they can form a continuing journey, so useful work and the reasons behind it do not disappear at the next handover.
Explore the architecture ↗Memory architecture and implementation work
Cortex separates capturing information, preserving its context, retrieving relevant records and caring for the resulting memory. Memory retrieval provides evidence to a task; it is a different mechanism from changing the parameters of a neural model.
Explore the architecture ↗Structural analysis tooling
GraFOSa represents code structure as related entities rather than isolated files. Questions about a change can then follow those relationships. An isolated graph alternative offers a place to examine a proposal while keeping structural analysis distinct from executing and testing software.
Explore the architecture ↗Idea-lineage research
Manthan separates generating contributions, relating them, preserving their origins and deciding which deserve further attention. Its lineage record is useful even when the quality of an idea remains unsettled. Selecting consistently useful ideas is a separate question from producing many of them.
Explore the architecture ↗Review mechanism
The panel separates review from adjudication. Different models examine the same subject; their findings are then challenged, consolidated and checked against that subject. The useful output is a traceable set of dispositions, not a vote that declares the work correct.
Explore the architecture ↗Engineering practice
This is an operating approach around engineering, not another platform successor. It separates work planning, implementation, independent review and completion decisions. The product architecture describes what is being built; the workforce approach describes how contributors work on it.
Explore the architecture ↗Shared-environment research
Spatial work combines a shared scene, participant interaction, proposed actions and a record of change. A shared view is only part of collaboration: participants also need to know who proposed a change, whether it was accepted and what context should survive.
Explore the architecture ↗Earlier platform work
Maestro approached coordination through specialist roles, workflow structure and continuing session context. The later Maestro Platform broadened the engineering foundation; Conduir carried forward implementation and architectural work from that history.
Explore the architecture ↗Research implementation
Investigate whether intelligence can acquire useful capabilities through smaller, explicitly controlled changes, while preserving the ability to examine what changed.
Explore the architecture ↗Research implementation
Make decisions under uncertainty inspectable by separating correct game mechanics, learned behaviour, evaluation and the experience a person uses.
Explore the architecture ↗Creation toolkit
Let creators focus on the experience they want to make while reusing common behaviour for play, input, display, saves and checking.
Explore the architecture ↗A composition to pursue
A view of the responsibilities needed for human possibility, continuing AI peers, collective intelligence and shared worlds to reinforce one another.
Explore the architecture ↗Historical proposal
An explanation of the proposed document-to-reviewed-information flow, with source support and human review at its centre.
Explore the architecture ↗Historical proposal
An explanation of the original idea for coordinating specialised AI assistance around a person’s goal.
Explore the architecture ↗