ARCHITECTURE OF THE VISION AI Initiative · conceptual direction A composition to pursue — Current projects contribute parts of this architecture. They do not yet establish one integrated, continuously learning system. A view of the responsibilities needed for human possibility, lasting AI peers, collective intelligence and shared worlds to reinforce one another. What would intelligence that grows with people need to do? The starting point is a person or community trying to accomplish something. A useful architecture must connect that purpose to relevant context, appropriate capabilities, actions that can be understood and outcomes that can change the next attempt. The four horizons describe different experiences of that ambition. They share some underlying responsibilities, but each has its own unresolved questions. Drawing them together is a design direction; the existence of individual projects does not establish that every connection operates today. BUILDING BLOCKS Human purpose and choice Keep the person’s intention, constraints and ability to redirect the work visible. Technical activity has value through the outcome it helps someone pursue. Receives: An ambition, context and chosen boundaries Produces: An understood objective and choices to resolve Learning and capability Develop or adapt an ability through an explicit learning process. Compare changes against the task and relevant prior abilities rather than equating more activity with improvement. Receives: A defined task, examples and an objective Produces: A candidate capability and an account of its behaviour Memory and context Retain useful records, decisions and their origins, with correction and forgetting treated as design responsibilities. Retrieval supplies context; it does not by itself retrain a model. Receives: Selected experience, permission and source context Produces: Relevant records with their meaning and limits Coordination and review Bring people and capabilities together, preserve the meaning of handovers and challenge proposed results. Different perspectives are useful when their claims can be examined. Receives: An objective, capabilities and proposed contributions Produces: An organised contribution and reviewed findings Shared environments Provide places where actions have observable consequences and participants can understand what changed. A game, a design space and a real-world system require different rules and levels of assurance. Receives: Participants, an environment state and permitted actions Produces: Visible changes and an interpretable outcome Evaluation and continuity Connect the result with the original intention and decide what should carry forward. Preserving context, modifying a procedure and training a model are separate kinds of change. Receives: Observed outcomes, expectations and review Produces: A decision about reuse, correction or further investigation WALKTHROUGH 1. Begin with a human purpose Understand the intended outcome and the choices the person wants to retain. A community exploring a shared space may need to compare alternatives, not delegate the final decision. The architecture should preserve that distinction throughout the work. 2. Bring context and capabilities Find the relevant information and capabilities for this situation. Memory may provide previous decisions; a model may propose options; an exact calculation may answer a bounded question. Each contribution needs a clear role and an account of its limits. 3. Develop and challenge options Coordinate contributions without treating model agreement as correctness. Keep the assumptions, sources and disagreements that matter to the choice. Where information conflicts, preserve the uncertainty so it can be resolved rather than smoothing it into a confident answer. 4. Act within understood boundaries Connect a selected proposal to an action only within the applicable rules and authority. A simulated layout change, a game move and a consequential external action are different commitments. The person must be able to understand what is proposed and what actually happened. 5. Learn from the outcome Compare the result with the intention and decide what to retain or change. A useful note may become memory; a repeated successful procedure may be considered for reuse; a model change needs a separate learning and evaluation process. None of these follows automatically from finishing a task. ILLUSTRATIVE EXAMPLE — Explore a community space A community wants to compare possible uses for a shared room. It has practical constraints and several competing preferences. Information support could collect the constraints and identify unresolved questions. Design capabilities could propose layouts, while calculation tools examine bounded questions such as capacity. Different participants could challenge the alternatives in a shared view. The community chooses what to try and records why; later experience informs the next discussion. A more understandable decision and a useful record of what was learned. This is an illustrative future journey. It does not claim that the current projects already provide this complete service or that AI can settle questions of community values. Human possibility: support an ambition A useful assistant needs more than an answer. It needs to understand the current task, expose meaningful options and help a person take a next step they can judge. Accessibility, effort and the ability to correct the system are part of that architecture. Games and creation tools are one current entry point. Research and professional systems approach other parts of the same question: how to turn intent into useful work without making the person decipher the machinery. Lasting AI peers: maintain a useful relationship A continuing collaborator would need context that survives individual sessions, abilities that can be developed, and a way to correct mistaken assumptions about the person. Memory, preferences and learning have related purposes but different mechanisms. A record of a conversation is not a trained skill. A retrieved preference is not permanent permission. Continuity needs to account for changes in people, models and tools rather than treating past context as unquestionable truth. Collective intelligence: make different contributions useful Coordination must preserve the purpose of the work and the responsibility for each contribution. Review should connect a concern to the work that supports or refutes it, rather than rely on how many agents agree. Conduir, the review work and idea-lineage research contribute different architectural responsibilities. A diagram showing them together describes a possible composition; useful integration needs its own examination. Shared worlds: connect ideas with consequences A shared environment needs a comprehensible state, rules for change and an account of who proposed or accepted an action. People and AI may perceive or interact with the space differently, so the boundary between a suggestion and an applied change matters. Game environments and spatial experiments provide bounded ways to study these questions. Success in a simulation does not automatically transfer to the physical world or justify an action outside the environment. Continuity is not a claim about consciousness Preserving a person’s writing, decisions or knowledge can support future understanding. That is a meaningful design problem without assuming the preservation or transfer of a person’s consciousness. The original speculative essays explore larger possibilities. They remain part of the history of the vision, while current architecture can address records, consent, provenance, correction and the practical limits of recall. SCOPE A shared architectural vocabulary connecting purpose, learning, memory, coordination, review and environments. Individual research and engineering projects that address different responsibilities. A route from accessible experiences to deeper technical investigations. REMAINING QUESTIONS A dependable composition across all responsibilities and horizons. Demonstrated benefit for particular people and tasks, including failure and correction. Learning and continuity that remain useful when models, tools, circumstances and preferences change. BOUNDARIES AND EVALUATION Composition: Capable parts can still disagree about meaning or fail when joined. Evaluation: Walk through a complete intended use and inspect the handovers, missing information and outcome. Human direction: A system can pursue a technically measurable result that misses what the person meant. Evaluation: Make the objective and unresolved choices visible, and examine whether correction changes the subsequent work. Kinds of improvement: Remembering a result, changing a process and training a model can be mistakenly described as the same learning event. Evaluation: State exactly what changed and evaluate it using a comparison appropriate to that mechanism. Speculation: An appealing future story can be read as a capability already delivered. Evaluation: Keep demonstrated work, proposed composition and philosophical questions visibly distinct. The vision gives the projects a shared direction without erasing their separate scope or attribution. Each guide explains one contribution and the limits of what it currently establishes. AI Initiative — public architecture guide.