Use whatever tool you want. It makes sure the work follows the process.
Eight phases. Each of the phases produces evidence.
Intent, Requirements, Plan, Execute, Verify, Validate, Approve, Evidence.
Independent verification. The checker should not be the producer. For level 4 safety-critical applications, that means a separate company.
Named human authority. Humans remain involved throughout the engineering workflow, with the context and evidence to guide the work, intervene when needed, and make consequential decisions.
Evidence that travels. All the evidence has to be stored, so that years later we can produce the evidence that this actually happened.
Kealu Vector is designed around five unresolved gaps in the current agentic engineering stack.
Independent verification. The checker should not be the producer. For level 4 safety-critical applications, that means a separate company.
Intent validation. Passing technical checks does not, by itself, establish that the correct problem was solved.
Named human authority. Consequential decisions remain subject to human authority.
Transferable evidence. Evidence should be inspectable by people who did not participate in the original work or decision.
Evidence freshness. Assurance evidence is not permanently valid.
Kealu Vector governs how agentic engineering work is framed, planned, performed, supervised, checked, evidenced, and presented to humans.
It sits between: Human intent and decision authority; Customer- or system-selected coding agents; Requirements, architecture, lifecycle, repository, quality, and compliance systems; Customer-owned and third-party testing, analysis, and verification systems; The evidence required to support consequential engineering decisions.
Kealu itself does not: Own the customer's test methods; Act as the responsible product-testing organization; Execute domain acceptance testing as the accountable party; Certify that the resulting software is correct; Assume responsibility for the software work product; Replace the human or organizational authority responsible for the final decision.
Kealu Vector is being developed through bounded early-access and enterprise-pilot engagements. The initial pilot focuses on the following intended product components, with implementation depth confirmed for each engagement:
Engineering Terminal. The Engineering Terminal is the human-facing assurance environment. It is designed to present: Active Assurance Work Packages, Intent and obligation status, Verification findings, Evidence completeness, Exceptions and residual risks, Required human decisions.
Chief Agent Engineer. The Chief Agent Engineer is the persistent engineering intelligence within Kealu Vector and steward of the Assurance Plane. It: Maintains engineering and assurance context, Frames and prioritizes Work Packages, Coordinates customer-selected coding agents, Preserves shared intent and architectural context as parallel work evolves, Briefs humans, Escalates matters when its authority or knowledge is insufficient.
Assurance Work Package. The Assurance Work Package is the atomic unit of work and value in Kealu Vector. Each consequential request, obligation, change, or environmental event can create a Work Package containing or referencing: The originating intent or trigger, Requirements and constraints, Applicable standards and internal policies, Required evidence, Verification findings, The resulting Assurance Case.
Assurance Case. The Assurance Case is the structured explanation of why an engineering outcome may be relied upon for a particular decision. The Assurance Case supports a human decision. It is not a Kealu certification or guarantee of product correctness. Explaining: What was intended, Which obligations applied, What work was performed, What evidence was generated, Whether the work remained aligned with intent, Which human or authorized role made each consequential decision.
Engineering Graph. The graph allows Kealu to determine which engineering obligations and prior assurance claims may be affected by a proposed or observed change. The Engineering Graph provides connected, persistent context across: Intent, Requirements, Architecture, Repositories, Tests and verification evidence, Standards and policies, Work Packages, Prior decisions.
Broader product roadmap: Evidence-freshness monitoring, Continuous re-assurance, API and Dependency Sentinel, Regulatory and Standards Monitor, Extensible specialist-agent framework.
Continuous re-assurance is outside the initial pilot scope. The implementation depth of the other listed capabilities, integrations, and deployment models is agreed per engagement.
Early access. Early-access participation is the intended route for selected users and organizations to evaluate Kealu Vector capabilities as the product and workflows are developed and refined. Access and available functionality are confirmed per engagement.
Enterprise pilot. Enterprise pilots are scoped engagements intended to apply Kealu Vector to a bounded, consequential engineering workflow within a customer environment. A pilot is an evaluation and development engagement, not evidence of a completed production deployment.
Retrospective project onboarding. Kealu is designed to govern a project from its setup and intent formation. Where necessary, selected elements of an existing project may be reconstructed and incorporated into the Kealu assurance framework through a customer-specific implementation project.
Consequential software change. Create and govern an Assurance Work Package for a feature, defect, interface change, architectural change, remediation activity, or other significant engineering event.
API or dependency change. Detect an external change, determine which systems and assurance claims may be affected, originate a Work Package, and coordinate the required investigation or remediation.
Regulatory or standards change. Identify which active or previously assured Work Packages may be affected by a revised standard, regulatory obligation, or internal policy.
High-consequence agentic development. Supervise customer-selected coding agents in safety-, security-, quality-, or compliance-sensitive environments while preserving evidence, separation of duties, and human authority.
Consequential software means systems where failure can affect safety, security, health, or material financial outcomes. This includes business-critical software with material financial-loss or security exposure; it does not mean that all enterprise software is consequential.
Primary customer segments: Regulated product-engineering organizations, Safety-critical software teams, Security-critical software teams, High-consequence enterprise-software organizations, Organizations deploying multiple coding agents into complex software-engineering environments.
Kealu integrates with customer-selected systems rather than requiring wholesale replacement of the engineering environment.
Integration categories include: AI coding agents, Source-code repositories, Requirements and lifecycle-management systems, Architecture and design repositories, Issue and change-management systems, CI/CD environments, Testing and verification systems, Static and security-analysis systems, Quality-management systems, Standards and policy repositories, Operational and in-service monitoring systems.
Kealu Vector is designed to support: Multi-tenant SaaS, Customer VPC, Private cloud, Customer-managed on-premise deployment, Air-gapped deployment, Customer-managed model endpoints, Bring-your-own-model deployment.
Early-access and enterprise-pilot engagement does not mean that the full platform, every integration, or every deployment option is already available.
Kealu Vector provides the working conditions and establishes the evidence required to trust agentic engineering work for complex systems, at scale.