Every Engineering With AI guide.
Browse the complete repository-backed library. Start with your role when you can; use this index when you already know the detail you need.
Adoption
Consultancy and multi-project rollout guideUse this guide when one delivery organisation supports several clients, business units, or independent projects with EWAI.Non-technical team guideUse this guide when you are contributing product, operations, risk, research, policy, or subject-matter knowledge without operating the EWAI command line yourself.
Blueprints
Building an internal Blueprint catalogueUse this guide to make reviewed Organisation Blueprint Packs discoverable across teams without confusing catalogue trust with project approval.Maintaining Organisation BlueprintsUse this guide after an Organisation Blueprint Pack is in use by one or more projects.Blueprint validation and troubleshootingUse this guide to diagnose an Organisation Blueprint Pack that is missing, rejected, incomplete, or unable to materialise during Discovery.
Core guides
Archaeology technology and hosting discoveryUse this capability during Archaeology to turn repository signals and accountable human answers into a governed view of the technology actually used and where it actually runs.Blast Radius and Impact Routing guideUse Blast Radius before changing an existing capability when you need to understand which repository paths, people, standards, and review responsibilities may be affected.Operational CLI referenceFor installation, personas, delivery and the full command-family map, use the CLI and configuration reference. This page covers the detailed error-report and Team Hub commands.Completed-phase evidence amendmentsEWAI treats a completed phase gate as durable delivery authority. If a referenced evidence file is legitimately corrected after phase completion, the delivery must not silently accept the new bytes and an operator must not edit the gate led…Review EWAI adoption across projectsUse Governed Rollout to see which projects use your organisation's agreed setup, which need reviewing and who should follow up. It compares the Organisation Blueprint each project has adopted with the version you've agreed for its group.…Context-Aware Delivery CompanionThis reference is for integration authors and engineers changing the Companion. For choosing and continuing work, start with the Companion user guide. The sections below describe the operating contract, ranking and implementation boundaries…Context-Aware Delivery Companion user guideThe Companion helps you understand what needs attention across an EWAI project, why it matters and who should act next. It gives you a ranked list of work so you can choose what to tackle without reading every delivery record.Context management and token efficiencyEWAI reduces repeated model input by assembling the minimum sufficient evidence for the work happening now. It does not shorten context by weakening engineering expectations. Standards, tests, security and privacy constraints, contradiction…Designing Organisation Blueprint PacksAn Organisation Blueprint Pack is a reviewed, reusable starting point for projects that share an organisation's engineering standards and perspectives. It is a strict local ewai.pack/v1 manifest plus bounded Markdown content.Developer delivery guideAsk EWAI to work through an intent with you. The ewai-deliver skill coordinates planning, implementation and review, checks what each stage needs, and asks for your approval before Build.…Local Error Reporting guideEWAI can create privacy-safe diagnostic packages without a paid service or hosted reporting backend. Reports remain on the user's machine until a person explicitly prepares an email or invokes a registered provider adapter.Error Reporting provider guideEWAI exposes a generic provider adapter boundary so an organisation can integrate its chosen commercial error tracker, ticketing tool or support service. The core product ships no connector, requires no paid service and provides no hosted r…Existing-project onboarding guideUse this guide when EWAI is joining a codebase whose behaviour, history, or purpose is not already represented by reliable project knowledge.Governed Starter-Project MaterialisationGoverned Starter-Project Materialisation turns an accepted Organisation Blueprint receipt into an immutable preview and, after named human approval, adds missing project files. It supports a single repository, a monorepo, and a workspace co…Complete guide catalogueChoose the section that matches your job. The optional team tools aren't prerequisites for working on a single project. User guides explain what to do. Integration references are also useful to engineers building adapters for their own orga…Guided Discovery facilitator guideUse this guide to lead an EWAI Discovery conversation without allowing the framework—or an active persona—to become the decision-maker.Guided Intent WorkspaceThe Guided Intent Workspace, labelled Intent Studio in the local dashboard, helps a product owner, facilitator, or engineer shape one feature intent without using the command line. It supports two bounded outcomes:Guided Phase Evidence DraftingThe dashboard's Contributions view lets business and technical colleagues add what they know to an active delivery. They can record evidence, questions and decisions, then hand the discussion to the next owner.…Human approval and assurance guideUse this guide when you are asked to approve Discovery, Build, curation, Manual QA, or another consequential EWAI action.Evidence-to-Knowledge Proposals implementer guideUse this guide when extending EWAI or building an integration for knowledge proposals. The CLI, MCP tools and dashboard all call the same domain module. That module validates destinations, review decisions and file changes; the interfaces m…Turn reviewed evidence into project knowledgeA meeting or retrospective can reveal a missing requirement, a useful working practice or a risk nobody had recorded. Knowledge proposals helps you turn that learning into proposed project documents, check each one and add only the changes…Meeting evidence implementer guideMeeting evidence is a project-local capability built around one domain contract and four adapters: CLI, MCP, loopback HTTP and the Mind Palace UI. The adapters do not implement their own review or promotion rules.Meeting evidence user guideUse Meeting evidence when you have meeting minutes or an existing transcript and want to turn useful statements into traceable project evidence without treating the conversation as automatic project truth.Organisation rollout guideUse this guide to introduce EWAI across several teams while keeping organisational consistency, project autonomy, and human accountability in balance.Persona entitlement and pack providersEWAI distributes premium personas separately from the public framework package. Distribution is website-only: this guide explains licence-checked Easy Digital Downloads (EDD)/WordPress delivery and the independent local verification control…Persona-guided prototype iterationEWAI reviews both the proposed prototype plan and the design that is actually produced. At each stage it identifies the most relevant available personas, shows why they are active, records their findings separately, and requires every findi…Power Platform and Salesforce export analysisEWAI can add bounded platform semantics to already-extracted Microsoft Power Platform and Salesforce source folders. The capability extends the existing Repository Source Map: it does not create a second index, connect to a tenant or org, e…Product Owner guideStart with the problem you want to solve, who experiences it and what a useful result would look like. You don't need every technical answer. Bring examples, explain what mustn't change, and identify the people who can answer the questions…Project and Portfolio Orchestration guideUse Project and Portfolio Orchestration when one outcome depends on several EWAI projects and you need a safe programme-level view of ownership, declared dependencies, evidence freshness and attention. The capability is read-only.…Repository Source Map guideThe Repository Source Map is EWAI's project-local inventory and analysis layer. It records every regular file found in the configured repositories, gives each file an explicit analysis outcome and depth, and uses deeper Tree-sitter evidence…Reproducible Archaeology and Discovery DepthEWAI can make the depth of Archaeology and Discovery explicit, proportionate, and repeatable. It does this without treating a long backlog as evidence of depth and without depending on identical prose from different model sessions.Screen prototype creation guideThis guide explains how EWAI turns an approved UI intent into a runnable screen prototype. It covers planning, design-system application, persona review, screen creation, rendered evidence, iteration and human acceptance.Security validation guideEWAI security validation coordinates evidence from security tools, records findings and accountable decisions, and can make configured evidence part of release readiness. It does not install scanners, certify a system, or replace profession…Solution Readiness Review guideBefore deciding what happens next, review the evidence for this delivery. Choose the type of system you're assessing; EWAI brings together the relevant records and shows what's missing or out of date.…Team Hub guideTeam Hub is EWAI's optional, self-operated team visibility layer. Every project remains in single mode by default: delivery runs locally, SPECS stay local, and no network service is required.…Team Hub Resource Registry guideThe Team Hub Resource Registry distributes immutable, organisation-owned EWAI working material without turning the Hub into project authority. The first release supports Organisation Blueprint packs with type: organisation and design-system…Using EWAI lifecycle hooksLifecycle hooks let an organisation-owned executable receive selected EWAI milestones after EWAI has recorded them. They are a provider-neutral handoff boundary, not built-in deployment, ticketing, messaging, security-scanning, or certifica…Working with personasPersonas give EWAI deliberate perspectives to apply during Discovery and delivery. They help expose blind spots, ask better questions, and translate consequences for different people.
Design systems
Design-system implementation guideThis guide is for maintainers integrating the portable capability into EWAI projects and hosts. It adds no server backend, connector, or design-system management UI: the supported boundary is local CLI/domain functions, installed skills, pr…Design-system pack authoring guideUse a pack when guidance should be reused across features or projects. Keep a one-off delivery decision local; promote it only after evidence shows it is a repeatable rule.Design-system review guideUse $ewai-design-system-review when a prototype or implemented surface exists. The review baseline is the immutable receipt linked by the selected artefact’s manifest, not whichever pack happens to be installed today.Design-system user guideUse a design-system pack when new screens should follow the product's existing design decisions. The pack can describe components, layout, wording, accessibility and how empty or error states should behave.…Product owner guide to EWAI design systemsA design system helps you make the intended product experience repeatable. It is broader than visual tokens and components: it can capture the experience promise, product principles, interaction behaviour, content, meaningful states, respon…
Examples
A minimal, non-sending error-report adapterThis example lets you validate an adapter package without a vendor account or network access. It always rejects transport. It must never report a ticket as created when nothing was sent.Review and promote one meeting statementThis complete example uses fictional notes in a disposable, initialised EWAI project. It demonstrates the file handoff; no meeting platform, model call or real person's approval is involved.…Install and select a small design-system packUse a disposable initialised project for this exercise. It shows the distinction between a candidate folder, an installed pack and an approved project selection. In a real project, review the guidance with its owner before selecting it.Complete prototype-review inputsThese are the four CLI input shapes for a prototype plan and one design cycle. They aren't ready-made approval records. Use them with an existing UI delivery whose intent and design-system guidance you've reviewed.Worked example: reproducible Archaeology and Discovery depthThis example shows how two sessions can produce different explanatory wording while reaching the same material investigation boundary. The project, people, IDs, and digests are illustrative; they are not a claim about a real system.Record one reviewed test scenarioUse this complete input shape after preparing scenarios for an existing intent. The fictional feature here is customer-access; it isn't a requirement your project inherits.Worked examplesThese compact scenarios demonstrate how to apply EWAI proportionately. They're illustrative decision patterns, not specifications to copy unchanged or exhaustive phase checklists. A stage omitted from an example isn't waived; follow the cur…
Explanation
The parts you'll use in EWAIThese terms turn up while you're working. You don't need to learn them all before starting a project.How delivery moves through fourteen stagesAsk EWAI to work through a feature with you. The ewai-deliver skill coordinates specialist skills and follows the saved project state. The runtime checks whether the required evidence and approvals exist; people remain responsible for requi…
Governance
Maintainers
Verify EWAI context preparationThis page is for engineers changing the harness's context selection or performance. Run source-checkout commands in the EWAI repository, not your application. For everyday inspection, see context management.Contributing to EWAIThis page is for engineers changing the EWAI harness itself. If you're using it in an application, start with the installation guide instead.Accept changes to EWAI evidence-depth behaviourThis is feature acceptance for EWAI maintainers, not a requirement for every application team running Archaeology. Use a disposable, privacy-safe fixture. The operator checklist covers reviewing an ordinary investigation.Verify changes to EWAIThese checks are for engineers maintaining the EWAI harness. They aren't extra setup or acceptance tasks for someone using EWAI on their own project.
Operations
Dashboard and delivery-state operationsUse this guide to inspect EWAI work, understand which state is authoritative, and recover projections without editing phase status by hand.Choose which dashboard views you needThe dashboard starts with its everyday tools. Extra views are off by default, so you don't have to navigate portfolio management, policy controls or integration tools when your project doesn't need them.Install and update EWAIEWAI is installed through npm. Your project's code and SPECS stay in your workspace; premium personas are an optional, separately licensed download.Set up and update premium personasIf you have a persona licence, you can enter it in the dashboard and install the pack straight away. You don't need to clone a repository or download files by hand.Troubleshooting and recoveryUse this guide when EWAI cannot check in, find project state, open the dashboard, resolve a pack or persona, or move a delivery forward.
Personas
Creating organisation-specific personasUse this guide to encode a reusable organisational perspective without turning a persona into an unreviewed policy engine.Persona authoring cookbookUse this guide to write a persona that improves questions and decisions without impersonating a stakeholder or becoming hidden policy.Persona engagement UI guideThis is an implementation and design guide for teams presenting EWAI's active personas in Guided Discovery, Blast Radius or another conversational surface. The response fields below describe the current contract.…Persona governance guideUse this guide to keep persona libraries useful, attributable, current, and appropriately bounded over time.
Policies
Governance Owner Guide to Policy Design GatesUse this guide when a proposed design needs your policy decision. Check which rule applies, which facts support the result and whether the required controls or an explicitly permitted exception address it.…Organisation Policy Design Gates Implementation GuideThis guide is for maintainers integrating or extending the capability without creating a second policy engine.Organisation Policy Design GatesOrganisation Policy Design Gates let a team test a proposed system design against its approved organisational rules before Build. They are optional: a project with no approved baseline reports not-configured and gains no policy blocker.Policy Pack Authoring GuideUse this guide to add a reusable policy contribution to an Organisation Blueprint Pack.Product Owner Guide to Policy Design GatesUse the Policy gates workspace to understand how an intended feature relates to organisational policy before engineering begins.Technical Owner Guide to Policy Design GatesCheck which version of your organisation's rules the design was assessed against, which controls are needed, and where the delivery plan addresses them. Use the technical policy view to inspect those links and resolve gaps before Build.
Quality
Manual QA and acceptance guideUse this guide to turn a technically completed delivery into evidence that an authorised person can inspect and accept.Persona-driven test scenariosUse persona-driven scenarios when a technically plausible test plan may still miss how a user, operator, maintainer, or specialist experiences the outcome. The process is especially useful for permissions, accessibility, privacy, recovery,…Review an Archaeology and Discovery depth runUse this checklist when preparing and reviewing an investigation in your project. It complements the general Manual QA and acceptance guide; it does not replace the canonical EWAI approval operation.
Reference
Capabilities and project layoutUse this reference when you need the detail behind a particular EWAI capability or want to understand its project files. For first use, follow your first session. The guide catalogue links the focused operating guides.CLI and configuration referenceThis is a compact map of the current public EWAI command families. Use the task-oriented guides for decision and safety context.Contributions APIFor integration authors and engineers changing EWAI's local dashboard. Contributors should use the Contributions guide.Write a security adapterThis reference is for engineers supplying an organisation-owned wrapper or translating an external tool's output into EWAI's contract. EWAI doesn't ship a universal scanner wrapper. To use an existing reviewed adapter, follow the operating…Write a starter-source adapterFor engineers implementing an organisation-owned source adapter. If someone supplies an approved adapter, follow the operating guide instead.
Standards
Tutorials
Work through your first featureFollow one fictional feature from a rough request to a reviewed delivery: export the filtered support-ticket list as CSV. This is a guided exercise, not a claim that the commands below generate a finished application.Your first EWAI sessionSet up a small, disposable project and find out what EWAI saves for you. You don't need an existing application, a Blueprint or a premium-persona subscription.