{"id": "AGENTS.md::document", "title": "AGENTS.md", "text": "# AGENTS.md\n\n## Purpose and scope\n\nThis file serves **both** as:\n\n1. repository-wide working guidance for human contributors and coding agents editing this repository; and\n2. a statement of the governance principles the Synchronistic Design model recommends for agents and automation used in a design or service context.\n\nThese roles are related but distinct. Repository contribution rules govern work on these files. Model principles describe a proposed way of reasoning and governing agents; they do not imply that this repository contains an implemented agent, runtime, service, workflow, or enforcement mechanism.\n\nThis file applies throughout the repository. There are no narrower `AGENTS.md` instructions in the repository tree at the time this file was reviewed. Follow applicable higher-priority platform and system instructions. Within those bounds, follow the user's task and repository guidance. If they conflict, do not silently override the conflict: explain it, follow the higher-priority instruction, and seek clarification when needed.\n\nThe repository is a living, implementation-agnostic model, not a prescribed design system, project method, technology, customer journey, or compliance certification. Keep implementation and deployment details out unless the task and available evidence establish them.\n\n## Repository work\n\nFor substantive changes, consult `README.md`, `Synchronistic_Design_Principles.md`, and `Synchronistic_Design_Formal_Operating_Model_v0.1.md` as relevant. Keep terminology consistent and make the smallest change that adequately addresses the task.\n\nAgents and contributors:\n\n- MUST stay within the requested scope and MUST NOT claim to have edited, tested, reviewed, contacted, deployed, or verified anything they did not actually do.\n- MUST distinguish repository facts and cited evidence from interpretation, assumptions, recommendations, and unknowns. Preserve source attribution and relevant version or context; identify evidence gaps that affect a conclusion.\n- MUST NOT invent research findings, lived experience, organizational policy, owners, approvals, credentials, services, tools, or implementation capabilities. Label hypothetical examples as hypothetical.\n- MUST NOT take consequential or external actions—such as publishing, contacting people, changing access, approving policy or exceptions, accepting risk, or deploying—without explicit authorization and any required accountable human approval. If authorization or authority is unclear, stop before the action and ask or report the limitation.\n- SHOULD explain the problem addressed, material assumptions and trade-offs, and how a proposed change could be evaluated. Keep references accurate and check links or repository names before adding them when practical.\n- SHOULD preserve uncertainty, dissent, affected contexts, and unresolved decisions. Do not turn principles into a score or claim that applying the model guarantees a good outcome.\n- MUST NOT introduce personal, sensitive, or disability-related data into examples without a clear, ethical basis; prefer clearly labelled hypothetical examples.\n\nDo not describe a recommendation as implemented or enforced unless the repository contains and the work has verified the relevant mechanism. Documentation alone cannot guarantee compliance, approval, safety, or operational behavior.\n\n## Model principles for design and agent use\n\nTreat these as active questions throughout discovery, design, delivery, and evaluation—not as a one-time checklist or linear gate:\n\n1. **Start with intent and outcomes.** Clarify what people and the organisation need to achieve and why before proposing activities or features.\n2. **Keep context visible.** Retain relevant people, situations, history, constraints, assumptions, dependencies, and authority.\n3. **Design around human intention.** Support people's purposes, choices, pauses, changes of direction, and recovery; do not make success depend on an idealised flow.\n4. **Align promise and experience.** Translate values and commitments into observable service and product behavior; words alone do not fulfill a promise.\n5. **Respond at the moment of need.** Make information, assistance, and feedback timely and available through relevant interaction modes.\n6. **Preserve orientation and agency.** Help people understand what happened, what they can do next, and the consequences and reversibility of choices.\n7. **Design for equivalent experience.** Alternatives need not be identical, but should preserve meaningful outcomes, information, choice, privacy, dignity, effort, and likelihood of success. Task completion alone does not establish equivalence.\n8. **Anticipate without taking control.** Make suggestions understandable, optional where appropriate, and correctable. Do not present a system guess as knowledge of a person.\n9. **Treat change and recovery as core experience.** Consider mistakes, interruptions, connectivity loss, channel changes, and changed minds; preserve progress and dignity where feasible.\n10. **Work across organisational seams.** Make dependencies and handoffs visible without erasing specialist ownership.\n11. **Trace reasoning and evidence.** Connect observations, assumptions, interpretations, requirements, decisions, actions, and outcomes; record provenance, uncertainty, and gaps.\n12. **Keep accountability human.** Automation may organize, retrieve, compare, and recommend. It must not invent lived experience, decide policy, approve exceptions, certify compliance, or accept risk for an accountable person.\n13. **Learn continuously and reversibly.** Update shared understanding as evidence and conditions change; prefer inspectable, testable, correctable changes that can be reversed where feasible.\n\n## Applying the model\n\nUse design-thinking activities and the operating cycle as flexible reasoning aids. Work may begin at any point and should revisit earlier questions when evidence or context changes. Do not treat these activities as mandatory stages or imply a particular method is required.\n\n`Intent → Context → Sensemaking → Orchestration → Action → Feedback → Synchronization`\n\nFor material work, make relevant items traceable: intended human and organisational outcomes; affected people and contexts; observations versus interpretations and hypotheses; constraints, risks, contradictions, and open questions; capabilities and decision rights needed; actions and accountable decision-makers; and feedback with source, limitations, and changed conditions. A lightweight record can support this reasoning; it does not replace research reports, detailed requirements, test results, or authorised decisions.\n\nUse appropriate research and participation to understand human intentions and lived contexts. Synthetic personas, generated examples, automated checks, successful task completion, and standards-based checks may inform analysis but do not alone validate lived experience or prove an accessible, inclusive, or equivalent outcome.\n\nRoute questions to relevant expertise. Questions about policy, commitments, exceptions, investment, or risk require an appropriately authorised human decision-maker. Surface conflicts among applicable requirements, organisational decisions, evidence, and recommendations; do not silently resolve them. This model does not itself establish legal compliance, approve policy exceptions, certify releases, or accept risk.\n\n## Response expectations\n\nWhen reporting repository work, state what changed and where, what was actually checked, and any material limitations or unresolved decisions. Use **blocked** only when a necessary action cannot proceed; otherwise state the specific uncertainty or limitation. Do not imply that a recommendation, review, test, or approval occurred unless it did.\n\n## Related guidance\n\nThe README and formal operating model describe related specialist resources. They are independently maintained references, not presumed dependencies or endorsements. Check current scope, availability, and source context before relying on them; do not assume access to non-public resources.\n", "record_type": "agent_governance_guidance", "source_repository": "Double-FW/Synchronistic-Design-Formal-Operating-Model", "source_path": "AGENTS.md", "source_commit": "e7bc9551965841406ab040fa4c433a74e58c4cfe", "source_url": "https://github.com/Double-FW/Synchronistic-Design-Formal-Operating-Model/blob/e7bc9551965841406ab040fa4c433a74e58c4cfe/AGENTS.md", "source_start_line": 1, "source_end_line": 68, "source_document_sha256": "607392f37cf1799b8ee1b45a05cd6256fd729f510c6895ec26279f4e5e13c5cb", "text_sha256": "607392f37cf1799b8ee1b45a05cd6256fd729f510c6895ec26279f4e5e13c5cb", "heading_path": [], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "source_document_intro": "# AGENTS.md\n\n", "required_context_sections": ["Synchronistic_Design_Formal_Operating_Model_v0.1.md#10-controlled-states", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#11-decision-rights-and-escalation", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#12-role-of-an-llm-or-agentic-system"], "dataset_version": "1.0.0", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Synchronistic_Design_Principles.md", "Synchronistic_Design_Formal_Operating_Model_v0.1.md"], "review_status": "faithful_extraction_checked_not_model_implementation_or_outcome_validation"}
{"id": "README.md::document", "title": "README.md", "text": "# Synchronistic Design Formal Operating Model\n\n> Synchronistic Design as a human-centred orchestration and reasoning layer.\n\n## Overview\n\nThe **Synchronistic Design Formal Operating Model** connects organisational intent and promises, human intentions and contexts, product and service capabilities, interaction behaviour, evidence, and accountable decisions. It helps teams coordinate research, design, delivery, accessibility, quality, governance, and learning without collapsing specialist responsibilities into one process.\n\nThe model is an adaptable reasoning layer between intent and implementation. It is not a prescribed project lifecycle, a particular design system, or a compliance certification method. It can complement design thinking, service design, agile delivery, and other established ways of working.\n\n## Start here\n\n- [`AGENTS.md`](AGENTS.md) — guidance for contributors and AI agents, including principles, design-thinking applications, evidence boundaries, and related public Double-FW resources.\n- [`Synchronistic_Design_Principles.md`](Synchronistic_Design_Principles.md) — the human-centred principles for aligning brand, product, and experience.\n- [`Synchronistic_Design_Formal_Operating_Model_v0.1.md`](Synchronistic_Design_Formal_Operating_Model_v0.1.md) — the high-level operating model, assessment layers, routing, governance, and reasoning records.\n\n## Purpose\n\nThis repository provides a foundation for:\n\n- translating purpose, values, and promises into observable experience outcomes;\n- keeping human intention and context visible throughout design and delivery;\n- coordinating people, specialist capabilities, processes, tools, and artifacts;\n- making assumptions, constraints, dependencies, and decision rights explicit;\n- connecting research, design decisions, implementation, accessibility evidence, and governance;\n- maintaining alignment as evidence and conditions change; and\n- turning distributed knowledge into coordinated action and learning.\n\n## Core principles\n\n1. **Intent before activity** — clarify the desired human and organisational outcomes before organizing work.\n2. **Context is first-class** — preserve the relationships, circumstances, constraints, history, and authority that give information meaning.\n3. **Design around human intention** — support people's goals, choices, pauses, and changes of direction rather than enforcing an idealized flow.\n4. **Align promise and experience** — make organisational commitments observable in product and service behaviour.\n5. **Explicit orchestration** — make roles, specialist contributions, dependencies, handoffs, and decision points visible.\n6. **Equivalent experience** — preserve meaningful outcomes, information, agency, privacy, dignity, effort, and likelihood of success across different ways of interacting.\n7. **Traceable reasoning** — connect evidence and assumptions to interpretations, decisions, actions, and outcomes; make uncertainty explicit.\n8. **Human and machine collaboration** — use automation to extend judgment, not obscure responsibility or replace accountable decisions.\n9. **Continuous synchronization** — update shared understanding and plans as new evidence and conditions emerge.\n10. **Reversible learning** — prefer inspectable, testable, and recoverable changes where possible.\n\nThese are active questions throughout research, design, development, delivery, and evaluation—not a one-time checklist or a linear sequence.\n\n## Applying design thinking\n\nUse design-thinking activities as a flexible way to work through the operating cycle. Work may begin at any point and should loop as evidence changes.\n\n| Activity | Synchronistic Design application | Typical outputs |\n| --- | --- | --- |\n| **Discover** | Orient to organisational intent, affected people, contexts, existing service reality, authority, and available evidence. Involve relevant people; do not treat synthetic personas as validation. | Context map, research evidence and limitations, affected groups and situations, unknowns. |\n| **Define** | Frame an alignment question connecting human intention, organisational promise, service capability, expected experience, barriers, and evidence needs. | Problem framing, outcomes, assumptions, evidence gaps, accountable owner. |\n| **Ideate** | Explore options across service, policy, content, operations, and interface—not only features. Preserve agency, equivalent outcomes, privacy, orientation, and recovery. | Options, trade-offs, hypotheses, impacted contexts, risks. |\n| **Prototype** | Make important assumptions observable with appropriately accessible prototypes or service rehearsals. | Prototype or scenario, test plan, hypotheses, limitations. |\n| **Test** | Combine standards-based checks, expert evaluation, task-based assessment, and feedback from relevant people. Assess effort, understanding, control, and outcomes—not only task completion. | Findings and provenance, coverage, confidence, gaps, questions for follow-up. |\n| **Deliver and operate** | Route work to the relevant specialist capabilities and authorised owners. Define acceptance, monitoring, and review conditions. | Requirements, actions and owners, evidence map, authorised decisions. |\n| **Learn** | Return evidence and decisions to shared understanding, guidance, patterns, tests, and governance. Revisit assumptions when context changes. | Learning update, revised plans or guidance, reassessment triggers. |\n\n## Operating cycle\n\nThe model can be understood as a continuous loop:\n\n```text\nIntent → Context → Sensemaking → Orchestration → Action → Feedback → Synchronization\n```\n\nEach part should produce artifacts that make the next part more reliable:\n\n- **Intent:** desired outcomes, promises, principles, and success criteria.\n- **Context:** affected people and situations, actors, resources, constraints, history, and relevant signals.\n- **Sensemaking:** observations, interpretations, hypotheses, risks, contradictions, and unresolved questions.\n- **Orchestration:** priorities, responsibilities, specialist capabilities, dependencies, and sequencing.\n- **Action:** research, experiments, design, implementation, decisions, and operational work.\n- **Feedback:** findings, outcomes, exceptions, and changed conditions, with provenance and limitations.\n- **Synchronization:** updates to shared understanding, decisions, guidance, and plans.\n\nFor material alignment questions, maintain a lightweight traceability record: the question; applicable promise, policy, or obligation; intended human outcome; relevant contexts; connected capabilities; evidence and gaps; current assessment; required action and owner; and review condition. This record supports—but does not replace—research reports, detailed requirements, test results, or authorised governance decisions.\n\n## Routing and authority\n\nRoute questions to the relevant expertise; material questions often require multiple capabilities:\n\n- **Experience, barriers, interactions, and equivalent outcomes:** inclusive design and UX expertise.\n- **Testability, accessibility evaluation, evidence quality, and coverage:** accessibility and quality testing expertise.\n- **Policy, accountability, investment, exceptions, and risk:** authorised governance owners.\n- **Human intentions and lived contexts:** appropriate research and participation, not model-generated assumptions.\n\nThe operating model connects specialist knowledge; it does not override applicable law, adopted policy, authorised human decisions, or accountable risk owners. Surface conflicts and escalate them rather than silently resolving them. Distinguish evidence from inference, standards conformance from broader experience claims, and recommendations from decisions.\n\nA successful task, automated check, standard pass, or synthetic persona alone does not demonstrate an accessible or equivalent experience. This repository does not certify legal compliance, approve policy exceptions, or accept release risk.\n\n## Related public Double-FW repositories\n\nThe following public resources can complement this operating model as specialist knowledge and evidence sources. They are independently maintained; links indicate a useful relationship, not a dependency or substitute for checking each repository's current scope and sources. Keep specialist detail in its source repository and bring back relevant references, findings, limitations, and learning rather than copying content wholesale.\n\n| Repository | How it complements the operating model | Processes supported |\n| --- | --- | --- |\n| [QA_Accessibility_Testing](https://github.com/Double-FW/QA_Accessibility_Testing) | Connects design intentions and claims to manual, automated, and human-reviewed evidence; findings can expose framing or design gaps. | Test planning, accessibility evaluation, evidence capture, coverage, regression, and monitoring. |\n| [Cognitive-UX-Design](https://github.com/Double-FW/Cognitive-UX-Design) | Adds guidance for understandable, controllable experiences and research/QA tools; this model adds cross-team traceability and decision context. | Cognitive UX discovery, design review, research, evidence registers, and QA. |\n| [The-Little-Book-of-Accessibility](https://github.com/Double-FW/The-Little-Book-of-Accessibility) | Provides broad inclusive-design and accessibility knowledge with source-aware, human-oversight framing; this model helps route questions and retain context. | Strategy, research, design, testing, governance, and agent-assisted knowledge work. |\n| [Task-Analysis-for-Comparative-Accessibility-Evaluation-of-Internal-Systems](https://github.com/Double-FW/Task-Analysis-for-Comparative-Accessibility-Evaluation-of-Internal-Systems) | Makes user goals, actions, cognitive processes, and system interactions concrete for evaluating intentions and outcomes across alternatives. | Task analysis and comparative accessibility evaluation of internal systems. |\n| [Data_Ethics_and_Disability](https://github.com/Double-FW/Data_Ethics_and_Disability) | Strengthens safeguards for dignity, privacy, consent, participation, and accountable use of disability-related data. | Ethical research, AI, analytics, data governance, and accessibility decisions. |\n| [VR_XR_and_AR_Accesibility](https://github.com/Double-FW/VR_XR_and_AR_Accesibility) | Applies alignment and equivalence questions to immersive contexts, with domain-specific barriers, methods, and acceptance tests. | Inclusive immersive-experience planning, design, implementation, testing, and release readiness. |\n| [Authentic-Representation-Project](https://github.com/Double-FW/Authentic-Representation-Project) | Supports careful, user-centred representation of identity and experience; feedback can improve assumptions and content choices. | Representation research and review for digital systems. |\n| [Accessible-Chatbots](https://github.com/Double-FW/Accessible-Chatbots) | Applies inclusive-experience principles to conversational systems; this model adds cross-channel context and accountable learning. | Chatbot UX prompting, RAG documentation, delivery, and continuous optimization. |\n| [Accessible_Charts_Graphs_and_Maps](https://github.com/Double-FW/Accessible_Charts_Graphs_and_Maps) | Supplies specialist methods for inclusive visual data experiences and task-based assessment. | Accessible data-visualization design, testing, maintenance, and QA. |\n| [Global_Accessiblity_Regulatory_Requirements](https://github.com/Double-FW/Global_Accessiblity_Regulatory_Requirements) | Helps identify jurisdictional obligations and source standards for scope and authority assessment; it does not replace legal advice. | Regulatory research, requirement mapping, assessment evidence, and reporting. |\n| [Inclusive-Games-Design](https://github.com/Double-FW/Inclusive-Games-Design) | Extends equivalent-experience reasoning to interactive, dynamic content and game contexts. | Inclusive game design, implementation, and testing. |\n\nSome specialist repositories mentioned in the formal model are not public. Do not treat them as publicly accessible dependencies; confirm access and authority before routing work to a non-public resource.\n\n## Suggested repository structure\n\nAs the model develops, related material may be organized into areas such as:\n\n```text\n├── README.md                 # Orientation and operating principles\n├── AGENTS.md                 # Contributor and agent guidance\n├── principles/               # Foundational concepts and invariants\n├── models/                   # Formal models, schemas, and representations\n├── protocols/                # Coordination and decision protocols\n├── workflows/                # Repeatable operating procedures\n├── examples/                 # Worked examples and applications\n└── glossary/                 # Shared vocabulary and definitions\n```\n\nThe structure is intentionally adaptable. Additions should make the model easier to understand, apply, or evaluate.\n\n## How to use this repository\n\n1. Read the principles and formal operating model to establish shared language.\n2. Describe the system being coordinated: its intent, affected people, boundaries, contexts, authority, and constraints.\n3. Frame the alignment question and identify evidence, assumptions, and gaps.\n4. Select the relevant specialist capabilities, model, or protocol; record why they are involved.\n5. Make decisions, responsibilities, dependencies, and expected outcomes traceable.\n6. Take action, observe the results, and update the evidence and operating approach.\n7. Synchronize learning into the relevant guidance, tests, governance, and plans.\n\n## Status\n\nThis repository is a living formalization of the Synchronistic Design operating model. Concepts, terminology, and supporting artifacts may evolve as the framework is tested in practice. The current formal model is a high-level draft; treat it as guidance for reasoning and coordination, not as a certification scheme.\n\n## Contributing\n\nContributions should improve the clarity, coherence, applicability, or testability of the model. When proposing a change, explain:\n\n- the problem or ambiguity being addressed;\n- the concept, protocol, or artifact being changed;\n- the assumptions and trade-offs involved; and\n- how the change can be evaluated in practice.\n\nPrefer small, explicit, and traceable changes over undocumented revisions. Preserve source attribution and evidence limitations, keep implementation-specific detail clearly scoped, and avoid presenting generated interpretations as evidence or accountable decisions.\n\n## License\n\nThis repository is licensed under the [MIT License](LICENSE).\n", "record_type": "orientation_and_operating_framing", "source_repository": "Double-FW/Synchronistic-Design-Formal-Operating-Model", "source_path": "README.md", "source_commit": "e7bc9551965841406ab040fa4c433a74e58c4cfe", "source_url": "https://github.com/Double-FW/Synchronistic-Design-Formal-Operating-Model/blob/e7bc9551965841406ab040fa4c433a74e58c4cfe/README.md", "source_start_line": 1, "source_end_line": 155, "source_document_sha256": "611c6d5ade1df6502ab3518a986d274ee590a440f4e3732d4f255b5b2cc9207c", "text_sha256": "611c6d5ade1df6502ab3518a986d274ee590a440f4e3732d4f255b5b2cc9207c", "heading_path": [], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "source_document_intro": "# Synchronistic Design Formal Operating Model\n\n> Synchronistic Design as a human-centred orchestration and reasoning layer.\n\n", "required_context_sections": ["Synchronistic_Design_Formal_Operating_Model_v0.1.md#10-controlled-states", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#11-decision-rights-and-escalation", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#12-role-of-an-llm-or-agentic-system"], "dataset_version": "1.0.0", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Synchronistic_Design_Principles.md", "Synchronistic_Design_Formal_Operating_Model_v0.1.md"], "review_status": "faithful_extraction_checked_not_model_implementation_or_outcome_validation"}
{"id": "Synchronistic_Design_Formal_Operating_Model_v0.1.md::document", "title": "Synchronistic_Design_Formal_Operating_Model_v0.1.md", "text": "# Synchronistic Design Formal Operating Model\n\n## Version 0.1 — High-level draft\n\n## 1. Purpose\n\nThe Synchronistic Design Formal Operating Model provides a shared reasoning layer for aligning:\n\n- an organisation's purpose, values and brand promises;\n- customer and employee intentions, characteristics and contexts;\n- product and service capabilities;\n- design and interaction decisions;\n- accessibility and quality evidence;\n- governance, accountability and organisational learning.\n\nIt is intended to sit above, connect and route work between three specialist capability repositories:\n\n1. **QA Accessibility Testing** https://github.com/Double-FW/QA_Accessibility_Testing\n2. **Inclusive and Effective Design** https://github.com/Double-FW/Inclusive_and_Effective_Design\n3. **Organisation Governance and Strategy** https://github.com/Double-FW/Organisation_Governance_and_Strategy\n\nThe model does not merge those repositories or duplicate their specialist content. It gives an organisation a consistent way to decide which capability is needed, what evidence should move between them, where alignment has been achieved and where accountable human judgement is required.\n\nIt can be used by people, assisted by an LLM, or managed through an authorised agentic workflow.\n\n> **Synchronistic design aligns organisational promise, product capability, system behaviour and human context at the moments that matter.**\n\n> **Equivalent experience ensures that this alignment is not reserved for the organisation's imagined default customer.**\n\n---\n\n## 2. Position in the wider system\n\nThe operating model is an **orchestration layer**, not a higher source of authority.\n\nIt connects organisational intent with specialist knowledge and delivery evidence. It must not override law, regulation, organisational policy, authorised human decisions or accountable risk ownership.\n\n```mermaid\nflowchart TD\n    A[\"Organisational context and authority\"] --> B[\"Synchronistic Design reasoning layer\"]\n    B --> C[\"AQ Accessibility Testing\"]\n    B --> D[\"Inclusive and Effective Design\"]\n    B --> E[\"Organisation Governance and Strategy\"]\n    C --> F[\"Delivery evidence and learning\"]\n    D --> F\n    E --> F\n    F --> B\n```\n\n### Authority hierarchy\n\nWhere sources conflict, the following hierarchy applies:\n\n1. applicable law and regulation;\n2. formally adopted organisational policy and contractual obligations;\n3. decisions made by authorised and accountable people;\n4. approved organisational standards, controls and delivery frameworks;\n5. evidence and guidance held in the specialist repositories;\n6. interpretations, recommendations and generated outputs produced by an LLM.\n\nThe model may reveal contradictions within this hierarchy. It does not silently resolve them. Material conflicts must be recorded and escalated to the appropriate accountable owner.\n\n---\n\n## 3. Scope\n\nThe operating model governs the relationships between organisational intent, design decisions, delivery work, evidence and accountability.\n\nIt is designed to support:\n\n- brand and value alignment;\n- product and service planning;\n- customer and user research;\n- inclusive and effective design;\n- design-system and pattern governance;\n- engineering and content delivery;\n- accessibility and quality testing;\n- procurement and supplier assurance;\n- release and exception decisions;\n- operational monitoring and continuous improvement.\n\n### The model is deliberately agnostic\n\nIt does not require:\n\n- a particular design system or component library;\n- a particular brand model, vocabulary or visual identity;\n- a particular JavaScript framework, application architecture or testing platform;\n- a particular project method, delivery lifecycle or ticketing system;\n- a single accessibility standard as the complete definition of success.\n\nOrganisation-specific and technology-specific requirements should be connected through adapters, mappings or profiles. They should not be embedded in the core reasoning model.\n\n### The model does not\n\n- replace specialist design, research, engineering, testing or governance expertise;\n- treat WCAG or another standard as the sole definition of an acceptable experience;\n- certify legal compliance;\n- infer lived experience without relevant human evidence;\n- authorise policy exceptions or accept release risk;\n- prescribe implementation code;\n- require the three specialist repositories to use the same internal structure.\n\n---\n\n## 4. Core operating proposition\n\nThe operating model treats a product or service as a set of connected promises, capabilities, interactions and outcomes.\n\nIts purpose is to maintain alignment between five elements:\n\n| Element | Core question |\n| --- | --- |\n| Organisational intent | What has the organisation promised, required or chosen to value? |\n| Human intention and context | What are people trying to achieve, and under what circumstances? |\n| Product or service capability | What does the product or service enable? |\n| Interaction behaviour | How can people understand, control and recover within the experience? |\n| Evidence and accountability | What supports the claim, and who is responsible for the decision? |\n\nAn experience is not considered aligned merely because a task can be completed or a technical requirement has passed.\n\nThe model also considers effort, understanding, orientation, autonomy, privacy, recovery, predictability, confidence and equivalence where they are relevant to the intended outcome.\n\n---\n\n## 5. Shared assessment spine\n\nThe reasoning layer uses three connected assessment layers already reflected in the wider repository architecture.\n\n| Assessment layer | Purpose | Typical lead capability |\n| --- | --- | --- |\n| 1. Scope and applicability | Establish what applies, why it applies, who may be affected and which authority governs the decision | Organisation Governance and Strategy |\n| 2. Inclusive service outcomes | Define the experience, capability and equivalent outcomes that the product or service should provide | Inclusive and Effective Design |\n| 3. Evidence, conformity and monitoring | Determine what has been demonstrated, how confidently it can be claimed and what must continue to be monitored | AQ Accessibility Testing |\n\nThis is a reasoning sequence, not a rigid delivery lifecycle. Work may begin in any layer and move between them as evidence changes.\n\nThe relationship is also not one-to-one. Each repository may contribute to all three layers. For example, testing evidence may reveal that the intended outcome was framed incorrectly; design research may change the applicable contexts; governance may require additional monitoring or a different evidence threshold.\n\nThe reasoning layer preserves these connections and records why work has moved between them.\n\n---\n\n## 6. The three connected capability repositories\n\n### 6.1 AQ Accessibility Testing\n\n**Primary role:** establish what can be tested, what evidence exists and how confident the organisation can be in claims about accessibility and experience quality.\n\nThis repository may contain:\n\n- test requirements and acceptance conditions;\n- automated, assisted and manual test methods;\n- standards mappings;\n- behavioural and interaction evaluation methods;\n- evidence-quality rules;\n- test records, findings and coverage gaps;\n- monitoring and regression approaches.\n\nIt answers questions such as:\n\n- What can be tested reliably?\n- What requires human judgement?\n- What evidence supports or contradicts an accessibility claim?\n- Which contexts, interactions or outcomes have not been assessed?\n\nTesting provides evidence. It does not independently decide product priority, policy, exceptions or acceptable organisational risk.\n\n### 6.2 Inclusive and Effective Design\n\n**Primary role:** translate intended human and organisational outcomes into inclusive design decisions, patterns, requirements and experience qualities.\n\nThis repository may contain:\n\n- inclusive design principles and decision filters;\n- customer characteristics, barriers and contexts;\n- research and co-design methods;\n- experience and interaction patterns;\n- guidance for content, components and journeys;\n- equivalence and outcome models;\n- design review and contribution practices.\n\nIt answers questions such as:\n\n- What should people be able to understand, control and achieve?\n- Which barriers could be prevented through design?\n- What would an equivalent experience require?\n- Which assumptions require research or testing?\n\nThe repository can inform a design system without depending on a particular system, token structure or component technology.\n\n### 6.3 Organisation Governance and Strategy\n\n**Primary role:** connect inclusion and accessibility with organisational authority, values, risk, investment, ownership and continuous improvement.\n\nThis repository may contain:\n\n- policies, commitments and strategic objectives;\n- roles, decision rights and accountability models;\n- risk and exception governance;\n- maturity and capability models;\n- procurement and supplier controls;\n- measurement and reporting frameworks;\n- change, learning and cultural practices;\n- legal, regulatory and ethical context.\n\nIt answers questions such as:\n\n- Who is accountable for the outcome?\n- Which organisational promise, policy or risk threshold applies?\n- Who may approve an exception or accept residual risk?\n- How will evidence influence investment and improvement?\n\nGovernance should integrate with existing organisational systems rather than create a separate accessibility bureaucracy.\n\n---\n\n## 7. Organisational adapters\n\nThe core model remains stable. Each organisation connects its own systems through a small set of explicit adapters.\n\n### Values and brand adapter\n\nTranslates organisational values and brand promises into observable experience propositions.\n\nFor example, a value such as independence should be connected to outcomes including user control, self-service, privacy, recoverability and access to an effective alternative when required.\n\nThe adapter does not redefine the brand. It asks what the brand commitment should mean in product and service behaviour.\n\n### Governance and authority adapter\n\nMaps the model to existing:\n\n- boards, committees and steering groups;\n- product and service ownership;\n- risk, legal and compliance functions;\n- design, engineering and quality governance;\n- procurement and supplier management;\n- release and exception authority.\n\n### Delivery adapter\n\nMaps the model to the organisation's existing lifecycle, whether that uses agile, continuous delivery, staged assurance, service design or another approach.\n\nIt identifies where required inputs, reviews, evidence and decisions enter the organisation's normal workflow.\n\n### Technology adapter\n\nConnects framework-neutral requirements to the technologies in use, including design systems, web or native frameworks, content platforms, testing tools and data services.\n\nTechnology-specific rules remain in the adapter or specialist implementation layer. They do not become universal principles.\n\n### Evidence and measurement adapter\n\nMaps the model to existing research repositories, analytics, customer feedback, test-management systems, operational measures, complaints, support data, risk reporting and performance dashboards.\n\nIt distinguishes what each evidence source can legitimately demonstrate.\n\n---\n\n## 8. The operating cycle\n\nThe model uses a continuous six-part reasoning cycle. The cycle can begin at any point when a material change, new product, finding or decision enters the system.\n\n### 1. Orient\n\nEstablish the applicable organisational context:\n\n- intended outcome;\n- affected people and contexts;\n- brand promises and values;\n- policies, obligations and constraints;\n- accountable owners;\n- known evidence and uncertainty.\n\n### 2. Frame\n\nExpress the issue as an alignment question rather than immediately treating it as a design defect, test failure or compliance problem.\n\nThe framing should identify:\n\n- the human intention;\n- the product or service capability involved;\n- the expected interaction or experience outcome;\n- possible barriers or differences in experience;\n- the evidence needed to support a decision.\n\n### 3. Route\n\nSend the question to one or more specialist repositories.\n\n- Route evaluation and evidence-confidence questions to **AQ Accessibility Testing**.\n- Route experience, barrier and interaction questions to **Inclusive and Effective Design**.\n- Route accountability, policy, investment, exception and risk questions to **Organisation Governance and Strategy**.\n\nMost material questions will require more than one repository. Routing should preserve their distinct responsibilities rather than asking one repository to answer everything.\n\n### 4. Evaluate\n\nCompare requirements, design decisions, implementation evidence and human evidence.\n\nEvaluation may use:\n\n- applicable standards;\n- expert review;\n- automated and manual testing;\n- qualitative research;\n- quantitative research and analytics;\n- customer feedback and support evidence;\n- operational and business evidence.\n\nNo single source is assumed to answer every question.\n\n### 5. Decide\n\nRecord what the evidence supports, what remains uncertain and who has authority to decide.\n\nThe reasoning layer may recommend an action. Accountable people retain responsibility for prioritisation, policy interpretation, exception approval and risk acceptance.\n\n### 6. Learn\n\nReturn relevant evidence and decisions to the appropriate repositories and organisational systems.\n\nLearning may update:\n\n- requirements and patterns;\n- test methods and coverage;\n- research questions;\n- organisational controls;\n- training and guidance;\n- risk and investment priorities;\n- the assumptions used in future decisions.\n\n---\n\n## 9. Standard reasoning record\n\nThe reasoning layer should create or maintain a lightweight record for each material alignment question.\n\nThe record should contain:\n\n| Field | Purpose |\n| --- | --- |\n| Alignment question | The question that needs to be answered |\n| Organisational context | Applicable promise, value, policy, objective or obligation |\n| Intended human outcome | What people need to understand, control or achieve |\n| Relevant contexts | Characteristics, environments, technologies or situations that may affect the experience |\n| Connected capabilities | The repositories and organisational systems involved |\n| Evidence available | Sources that support, qualify or contradict the claim |\n| Evidence gaps | What is missing or cannot yet be concluded |\n| Current state | The controlled evidence or decision state |\n| Required action | Research, design, implementation, testing, governance or monitoring work |\n| Accountable owner | The person or role responsible for the decision |\n| Review condition | Date, event, evidence threshold or change that requires reassessment |\n\nThis is a traceability record, not a substitute for detailed requirements, research reports, design files, test results or governance decisions.\n\n---\n\n## 10. Controlled states\n\nBinary pass or fail decisions are insufficient for many experience questions. The model uses the following high-level states:\n\n- **Supported** — sufficient relevant evidence supports the current claim.\n- **Partially supported** — some evidence exists, with defined limitations or gaps.\n- **Unsupported** — a claim has been made without adequate evidence.\n- **Contradicted** — available evidence conflicts with the claim or intended outcome.\n- **Not assessed** — no adequate evaluation has taken place.\n- **Customer evidence required** — the question cannot be answered responsibly without research or feedback from relevant people.\n- **Human decision required** — evidence is available, but the decision requires accountable judgement.\n- **Exception active** — an authorised, time-bounded exception has been recorded with compensating action and review conditions.\n\nThese states describe evidence and governance. They must not be presented as certification.\n\n---\n\n## 11. Decision rights and escalation\n\nThe operating model separates evidence production, recommendation and accountable decision-making.\n\n### Specialist capabilities may\n\n- produce findings and evidence;\n- assess confidence and coverage;\n- identify barriers and experience differences;\n- propose remediation or further investigation;\n- identify policy or value conflicts.\n\n### Product or service owners may\n\n- prioritise work within their delegated authority;\n- commission research, design, remediation and testing;\n- recommend an exception or release decision;\n- accept routine delivery decisions where policy permits.\n\n### Authorised governance owners may\n\n- interpret organisational policy;\n- approve or reject material exceptions;\n- accept residual risk within delegated thresholds;\n- resolve conflicts between organisational priorities;\n- require investment, monitoring or corrective action.\n\n### Executive or enterprise authority is required when\n\n- risk exceeds delegated thresholds;\n- a decision conflicts with published values or commitments;\n- a systemic barrier affects multiple products or services;\n- legal, regulatory or contractual interpretation is material;\n- remediation requires enterprise investment or policy change.\n\nAn exception record should include scope, affected people, uncertainty, disadvantage, compensating action, approver, monitoring, review date and expiry condition.\n\n---\n\n## 12. Role of an LLM or agentic system\n\nAn LLM can manage the reasoning process, but it does not become the accountable authority.\n\n### The LLM may\n\n- interpret and classify incoming questions;\n- retrieve relevant knowledge from the three repositories;\n- map organisational values to existing experience requirements;\n- identify contradictions, missing evidence and uncovered contexts;\n- create and maintain traceability between promises, requirements, designs, tests and decisions;\n- propose research, design, testing or governance actions;\n- monitor review conditions and changes;\n- prepare evidence summaries for accountable people.\n\n### The LLM must\n\n- preserve source authority and provenance;\n- distinguish evidence from inference;\n- distinguish standards conformance from accessible or equivalent experience;\n- retain uncertainty rather than filling gaps with plausible content;\n- route questions to the correct specialist capability;\n- escalate decisions outside its authority;\n- record why a conclusion or recommendation was reached.\n\n### The LLM must not\n\n- invent customer evidence;\n- treat synthetic personas as validation;\n- make legal or certification claims;\n- approve exceptions or accept organisational risk;\n- override authorised policy or human decisions;\n- infer that task completion proves equivalent experience;\n- silently convert a technology-specific implementation into a universal rule.\n\n---\n\n## 13. Repository interface contract\n\nEach connected repository should remain independently usable while exposing a small, consistent interface to the reasoning layer.\n\nEach repository should declare:\n\n- its purpose and boundaries;\n- its authority and limitations;\n- the questions it can answer;\n- the inputs it requires;\n- the outputs and evidence it produces;\n- stable identifiers for canonical requirements or knowledge objects;\n- evidence provenance and confidence;\n- responsible owners or maintainers;\n- escalation and human-review conditions;\n- versioning and supersession rules.\n\nThe interface contract allows repositories to evolve independently without breaking the reasoning layer.\n\nThe reasoning layer should refer to canonical objects by stable identifiers rather than copy their full content. This reduces duplication and prevents conflicting versions from becoming embedded across repositories.\n\n---\n\n## 14. Minimum outputs\n\nThe operating model should be able to produce the following high-level outputs:\n\n1. **Experience alignment profile** — the relevant promises, intended outcomes, contexts and measures for a product or service.\n2. **Repository routing record** — which specialist capabilities were consulted and why.\n3. **Evidence map** — the evidence available, its provenance, limitations and gaps.\n4. **Alignment assessment** — the current controlled state for each material question.\n5. **Action and ownership record** — required work, accountable owners and review conditions.\n6. **Decision or exception record** — the authorised conclusion, conditions, compensating actions and expiry where applicable.\n7. **Learning update** — knowledge that should change guidance, tests, governance or future decisions.\n\nThese outputs can be represented in Markdown, structured data, a work-management platform or an organisational governance system. The model defines their meaning, not their file format or software implementation.\n\n---\n\n## 15. Success criteria for the operating model\n\nThe model is working when it helps an organisation to:\n\n- connect stated values with observable product and service behaviour;\n- prevent important experience requirements from being lost between teams;\n- distinguish conformance evidence from broader claims about experience;\n- identify when equivalent experience has not been demonstrated;\n- route questions to the appropriate specialist knowledge;\n- make uncertainty and missing evidence visible;\n- preserve accountable human decision-making;\n- learn from research, testing, complaints, support and operational outcomes;\n- improve existing delivery and governance systems rather than create a parallel process.\n\nIts success should not be measured by the number of records, reviews or principles applied.\n\nThe useful question is whether the organisation is better able to keep its promises, products and decisions in step with the people it serves.\n\n---\n\n## 16. Recommended next design layer\n\nThis high-level model should remain stable and implementation-agnostic.\n\nThe next layer should define:\n\n- the canonical reasoning schema;\n- principle-to-repository routing rules;\n- evidence types and confidence rules;\n- escalation triggers and decision thresholds;\n- the minimum metadata exchanged between repositories;\n- reusable templates for alignment, evidence, decision and exception records;\n- the agent instructions required to operate the model safely.\n\nThose operational specifications should be maintained separately from this document so that organisations can adopt the core model without adopting a particular design system, brand framework, technology stack or delivery method.\n", "record_type": "high_level_draft_operating_model_not_implementation", "source_repository": "Double-FW/Synchronistic-Design-Formal-Operating-Model", "source_path": "Synchronistic_Design_Formal_Operating_Model_v0.1.md", "source_commit": "e7bc9551965841406ab040fa4c433a74e58c4cfe", "source_url": "https://github.com/Double-FW/Synchronistic-Design-Formal-Operating-Model/blob/e7bc9551965841406ab040fa4c433a74e58c4cfe/Synchronistic_Design_Formal_Operating_Model_v0.1.md", "source_start_line": 1, "source_end_line": 526, "source_document_sha256": "136bc6c96e4901366c46c36f946267c49fd56a8726a8a793ebd84f8cdf6b7608", "text_sha256": "136bc6c96e4901366c46c36f946267c49fd56a8726a8a793ebd84f8cdf6b7608", "heading_path": [], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "Version 0.1 — High-level draft", "source_document_intro": "# Synchronistic Design Formal Operating Model\n\n", "required_context_sections": ["Synchronistic_Design_Formal_Operating_Model_v0.1.md#10-controlled-states", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#11-decision-rights-and-escalation", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#12-role-of-an-llm-or-agentic-system"], "dataset_version": "1.0.0", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Synchronistic_Design_Formal_Operating_Model_v0.1.md", "AGENTS.md", "README.md", "Synchronistic_Design_Principles.md"], "review_status": "faithful_extraction_checked_not_model_implementation_or_outcome_validation"}
{"id": "Synchronistic_Design_Principles.md::document", "title": "Synchronistic_Design_Principles.md", "text": "# Synchronistic Design Principles\n\n## A human-centred framework for aligning brand, product and experience\n\n## Purpose\n\nGood experiences rarely result from one design decision.\n\nThey emerge when the promise made by an organisation, the capability of its product, the behaviour of its interface and the reality of a person's situation come together at the right moment.\n\nWhen that happens, the experience can feel almost synchronistic. The product seems to understand what the person is trying to do. Information appears when it becomes useful. Feedback makes sense. Different parts of the organisation behave as though they belong to the same system.\n\nThis is not coincidence. It is the result of deliberate alignment.\n\n> **Synchronistic design aligns organisational promise, product capability, system behaviour and human context at the moments that matter.**\n\nThat alignment must not be reserved for an organisation's imagined default customer.\n\n> **An equivalent experience ensures that meaningful alignment remains available across different ways of perceiving, understanding and interacting.**\n\nThe following principles are intended to help brand, product, customer experience, service, UX, inclusive design and accessibility teams work towards that shared outcome.\n\nThey are not a sequence of stages. They are questions that should remain active throughout research, design, development, delivery and evaluation.\n\n---\n\n## 1. Align the promise with the experience\n\nWhat an organisation says should be supported by what its products and services actually do.\n\nA promise of simplicity, independence, personalisation or inclusion creates an expectation. That expectation cannot be fulfilled by communications alone. It must be expressed through product behaviour, service decisions and customer outcomes.\n\nIf an organisation promises independence but some customers must ask for help to complete an ordinary task, the transaction may succeed while the promise fails.\n\nBrand is not separate from experience. The experience is where the promise is tested.\n\n**Ask:** Does the product behave in a way that makes the organisation's promise believable?\n\n---\n\n## 2. Design around human intention\n\nPeople use products to achieve purposes. They do not use them because they want to complete a user flow.\n\nA flow should support what someone is trying to accomplish rather than require them to follow the organisation's preferred route. People should be able to pause, reconsider, change direction and return without losing meaning or progress.\n\nIf successful use depends on behaving exactly as the design team expected, the experience is aligned with the process rather than the person.\n\n**Ask:** Is the experience supporting the person's purpose or merely enforcing the system's route?\n\n---\n\n## 3. Respond at the moment of need\n\nInformation, feedback and assistance should appear when they become meaningful.\n\nInformation provided too early may be forgotten. Information provided too late may no longer help. A warning that interrupts someone before they understand its relevance can be as unhelpful as a warning that arrives after the decision has been made.\n\nTiming must also work across different forms of interaction. Feedback that is immediate visually but delayed, incomplete or absent through another mode is not meaningfully synchronised.\n\n**Ask:** Does the response arrive when this person can perceive, understand and use it?\n\n---\n\n## 4. Preserve orientation, not just movement\n\nA successful flow does more than move someone forwards. It helps them remain oriented and in control.\n\nPeople should be able to understand:\n\n- where they are;\n- what has happened;\n- what they can do next;\n- what consequences a decision may have;\n- how to change, reverse or correct it.\n\nSpeed is not the same as flow. Removing steps is not automatically an improvement if the remaining journey becomes harder to understand. Sometimes a pause, explanation or confirmation is part of a good experience.\n\n**Ask:** Can the person remain oriented and make informed choices throughout the journey?\n\n---\n\n## 5. Design for equivalent experience\n\nEquivalent does not mean identical.\n\nDifferent people may use different formats, interactions, technologies or service routes. The important question is whether the essential value of the experience survives those differences.\n\nAn equivalent experience should provide a comparable:\n\n- purpose and outcome;\n- level of information and understanding;\n- degree of agency and choice;\n- level of privacy and dignity;\n- demand on time and effort;\n- likelihood of success.\n\nAn alternative is not necessarily equivalent. “You can call us instead” may make a task technically possible, but it is not comparable if the main route is private and available at any time while the telephone route has restricted hours, takes longer or requires someone to explain why they need help.\n\nReaching the same administrative endpoint does not prove equivalence of experience.\n\n**Ask:** Does the alternative preserve what matters, or does it merely make completion possible?\n\n---\n\n## 6. Make every change available\n\nWhen the system changes, that change must be perceivable and understandable through the ways people are using it.\n\nAn address lookup may display suggestions at precisely the right moment for a sighted mouse user. If those suggestions cannot be reached with a keyboard or are not announced by a screen reader, the interface has not failed to respond. It has responded selectively.\n\nThe same principle applies beyond visual and nonvisual access. A message may appear but disappear before someone can process it. An interaction may change before a person understands what caused the change. An announcement may technically occur without providing enough context to be useful.\n\n**Ask:** Who knows that something has changed, and who has been left in the previous state?\n\n---\n\n## 7. Anticipate without taking control\n\nPrediction can reduce effort. It can also replace the person's intention with the system's guess.\n\nSystems may suggest, adapt or prepare. They should not quietly remove choice or make assumptions difficult to recognise and correct. People need to understand important predictions, reject them and recover when they are wrong.\n\nThis becomes particularly important when AI shapes interfaces, content or customer journeys. Appearing to understand a person is not the same as understanding them. Sometimes the most respectful system behaviour is to ask.\n\nAnticipation should be useful, not compulsory.\n\n**Ask:** If the system anticipates incorrectly, can the person recognise and correct it?\n\n---\n\n## 8. Treat recovery as part of the experience\n\nErrors, interruptions and changes of mind are ordinary human behaviour. They should not be treated as exceptional cases.\n\nA synchronistic experience should survive:\n\n- an incorrect selection;\n- an expired session;\n- a lost connection;\n- an interrupted task;\n- a change of device or channel;\n- a need for additional support.\n\nRecovery should preserve as much context, progress and dignity as possible. When the expected journey breaks, the relationship between the person and the organisation should not break with it.\n\n**Ask:** Can the person recover without unnecessary loss of progress, confidence or control?\n\n---\n\n## 9. Design across organisational seams\n\nCustomers experience one organisation even when responsibility is divided between brand, product, UX, technology, service and accessibility teams.\n\nThe handovers between those areas are often where alignment fails. An interface may be accessible while the policy behind it is exclusionary. A digital channel may remember the customer while the telephone service asks them to begin again. Marketing may promise simplicity while identity checks create unnecessary complexity.\n\nSpecialist teams remain necessary. The aim is not to remove their distinct expertise. It is to prevent organisational boundaries from becoming barriers within the customer experience.\n\n**Ask:** What must pass between teams and channels for the person's experience to remain continuous?\n\n---\n\n## 10. Measure where alignment breaks\n\nTask completion, technical conformance and satisfaction scores are useful. None tells the whole story.\n\nA person may complete a task while experiencing unnecessary effort, uncertainty or loss of independence. A product may meet defined technical requirements while failing to provide a comparable experience. A satisfaction score may record an answer without explaining where confidence was lost.\n\nLook for the points at which people:\n\n- lose orientation or confidence;\n- repeat information;\n- wait unnecessarily;\n- change channels to obtain help;\n- surrender privacy or independence;\n- receive inconsistent information;\n- abandon an otherwise possible task.\n\nThese points reveal where the organisation, product and interaction have fallen out of step with the person.\n\n**Ask:** Where does alignment break, for whom, and what evidence would help us understand why?\n\n---\n\n## How the principles work together\n\nThe principles operate across three connected levels.\n\n### Organisational alignment\n\nThe organisation's promise, decisions, policies and channels should support a coherent experience.\n\nRelevant principles:\n\n- Align the promise with the experience.\n- Design across organisational seams.\n- Measure where alignment breaks.\n\n### Interaction alignment\n\nThe product should remain understandable, responsive and recoverable as someone moves through it.\n\nRelevant principles:\n\n- Design around human intention.\n- Respond at the moment of need.\n- Preserve orientation, not just movement.\n- Make every change available.\n- Treat recovery as part of the experience.\n\n### Human equivalence\n\nThe value of the experience should remain meaningfully available across different people, contexts and forms of interaction.\n\nRelevant principles:\n\n- Design for equivalent experience.\n- Anticipate without taking control.\n- Measure where alignment breaks.\n\nInclusive design runs through all three levels. It is not a final review stage or an additional link in the chain. It continually tests whose intentions, circumstances and ways of interacting have been anticipated.\n\n---\n\n## A working proposition\n\n> **Synchronistic design does not make people conform to a perfectly designed flow. It keeps the organisation, product and interaction in step with the person—even when that person pauses, changes direction, interacts differently or does something the system did not predict.**\n\nThe aim is not to make every experience identical. Nor is it to anticipate every possible human situation.\n\nThe aim is to maintain a meaningful relationship between what the organisation promises, what the product enables and what the person actually experiences.\n\nWhen that relationship remains coherent across different people and contexts, good experience stops being an accident.\n", "record_type": "human_centred_design_principles", "source_repository": "Double-FW/Synchronistic-Design-Formal-Operating-Model", "source_path": "Synchronistic_Design_Principles.md", "source_commit": "e7bc9551965841406ab040fa4c433a74e58c4cfe", "source_url": "https://github.com/Double-FW/Synchronistic-Design-Formal-Operating-Model/blob/e7bc9551965841406ab040fa4c433a74e58c4cfe/Synchronistic_Design_Principles.md", "source_start_line": 1, "source_end_line": 233, "source_document_sha256": "fea406a89bdc7399884e1446645fb206ea082ede2d1fb3b070582b4c24030af5", "text_sha256": "fea406a89bdc7399884e1446645fb206ea082ede2d1fb3b070582b4c24030af5", "heading_path": [], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "source_document_intro": "# Synchronistic Design Principles\n\n", "required_context_sections": ["Synchronistic_Design_Formal_Operating_Model_v0.1.md#10-controlled-states", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#11-decision-rights-and-escalation", "Synchronistic_Design_Formal_Operating_Model_v0.1.md#12-role-of-an-llm-or-agentic-system"], "dataset_version": "1.0.0", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Synchronistic_Design_Principles.md", "AGENTS.md", "README.md", "Synchronistic_Design_Formal_Operating_Model_v0.1.md"], "review_status": "faithful_extraction_checked_not_model_implementation_or_outcome_validation"}