Founding technical access

Build the environment
around the agent.

Aware makes approved business meaning, versioned change, policy, agent work, and Service outcomes one explicit architecture over the systems your team already runs.

Book a technical workflow review Inspect source

The source-to-reaction architecture

An agent runtime is not the customer environment.

Agent frameworks reason and execute. Aware provides the surrounding operational substrate: persistent domain identity, approved meaning, policy, typed tools, Human control, and a traceable outcome.

01Source observation

Bounded evidence arrives from the existing system while that system remains fact authority.

02Ontology + Workspace

Domain owners approve objects, relationships, capabilities, and exact realizations.

03Versioned semantic change

Before-and-after meaning is explicit, attributable, and reusable across reactions.

04Reactivity

Conditions and policy turn meaningful change into an authorized action intent.

05Agent / Inference

A provider reasons over finite typed context and proposes one permitted capability.

06SDK → API → Service

Typed admission, fulfillment, observed outcome, and feedback complete the chain.

The bounded agent boundary

Typed context in.
Typed proposal out.

The agent sees the event, approved meaning, policy, relevant operational view, and allowed capabilities. Authority stays in Identity, API, Service, and the source system.

agent_contextconceptual contract

event        fulfillment.order_at_risk
change       shipment.eta +36h
meaning      priority order #3812
policy       delay_over_24h
capabilities [inspect_options,
              prepare_response]
correlation  exact + idempotent

Agent returnstyped capability proposal + explanation

Three public doors

Choose the boundary that matches your work.

Creator

aware-dev

Declare business meaning, materialize owned packages, evaluate evidence, and evolve accepted Workspace revisions.

Contributor setup

Integration

Typed SDK / API / Service

Consume declared capabilities without depending on repository internals or provider-specific agent state.

Trust & Architecture

Inhabitant

aware-sdk

Let Humans and agents enter one operational World through lawful, actor-specific Experience.

Shared Attention

Open-source foundations

Inspect the architecture. Contribute to the system.

Source

Explore the repository

Read the semantic packages, services, runtime boundaries, and evidence infrastructure directly.

Open GitHub

Architecture

Follow the two loops

See how semantic source becomes committed graph truth, then how typed actions evolve operational state.

Code → Graph → Commits Actions → Commits → Outcomes

Contributor setup

Bootstrap aware-dev

Use the repository contributor entrypoint to join the development workflow and inspect the creator toolchain.

curl -fsSL https://aware.run/install-aware-dev.sh | bash

Founding technical program

Have one workflow where business change should invoke AI?

Bring the source, meaningful change, Human authority, current agent behavior, and desired response. We will make the first implementation boundary explicit.

Book a workflow review

Reactive AI Design Sprint · USD 5,000 · two weeks · first three founding partners

Please do not submit credentials, customer data, or confidential system details when booking.

Email [email protected]Product Trust & Architecture