Skip to main content
Human-AI Co-Construction (HAI-Co²) frames human-AI collaboration as the joint construction of a single shared solution. Rather than the human prompting and the model replying, both parties read and write the same typed workspace and refine one artifact together until it meets a goal they co-own.

​
The four shared surfaces

Everything the human and the agent collaborate over lives in four surfaces, each a concrete UI panel backed by concrete state. Both sides can read and edit all of them.

Objective & constraints: Uᵗ

The agent’s one-line read of the goal (the Objective) plus the decoded preferences (hard / soft constraints). Co-owned: the agent proposes, the user can edit or lock.

The plan: X_j

A depth-ordered, numbered plan of todo steps, the agent’s own execution ledger, ticked off as it works.

The working artifact: X̂

The document (and typed artifacts such as charts) in the centre panel, the object being built together.

The conversation: I

The chat and its full message history (the informational state), the channel used to negotiate everything else.
Both parties read and write the one shared workspace, and the agent advances it by running a ReAct turn over those four surfaces:

​
How the implementation maps to the model

See Architecture for how these pieces connect, and Agent core logic for what the agent sees and does on each turn.

​
How it differs from RLHF and assistance games

  • vs. RLHF: in RLHF humans rank finished model outputs to shape a reward; in HAI-Co² the human and agent jointly edit the artifact and the objective in-flight, so feedback is the shared work itself, not an after-the-fact preference label.
  • vs. assistance games: assistance games have the AI infer a fixed, hidden human reward. Here the utility Uᵗ is explicit and co-owned: the Objective and constraints are visible, user-editable, and revised as the work evolves rather than guessed at.
A deeper rationale (the defining characteristics, the ethics-by-partnership stance, and the application domains) is on the About page of the live app and in the formal paper that accompanies the project.