Product.ai / Join / Projects / Agent Confidence-Signaling Component — how Alloy speaks confidence to other AI agents and to the human in the loop
Project Open to Alpha Team

Agent Confidence-Signaling Component — how Alloy speaks confidence to other AI agents and to the human in the loop

Design and ship a confidence-signaling component for Alloy — Product.ai's local-first agentic workbench. The component carries calibrated confidence from Alloy through to two audiences simultaneously: (1) the human in the loop, who needs to see when to verify, and (2) the downstream AI agent or MCP consumer, who needs a machine-readable confidence + evidence payload to make its own decision. Same primitive, two surfaces, no duplication.
Project Overview
Discipline
Design — Head of Product Design · AI Systems — AI Engineer
Duration
2 weeks
Compensation
Your stated freelance rate
Surface
Agent commerce · Truth Graph · Product.ai
Kernels
agent-commerce · truth-graph · productai
Outcomes
dev-integrate · truth-graph-depth · multi-surface
Tier
Consequential
Alpha Team
Open to alpha members who want to take this on
Tooling
Claude Code or Co-work

Why we want this done

Agent commerce is structurally selecting against browser automation and toward protocol commerce (agent-commerce kernel A-1). Protocol economics are 10-100x cheaper, more reliable, and more reputationally durable. As that shift accelerates, Product.ai's surface that other AI agents call most often is the one whose confidence semantics matter most. Alloy is that surface. Today, Alloy returns answers; it does not yet carry the confidence semantics needed for an upstream agent to know when to escalate to the human or to a different source. The Agent Confidence-Signaling Component closes that gap. It also tests the most ambitious instance of multi-surface coherence — the same trust primitive serving an end user AND a machine consumer simultaneously, with no language-mismatch on the seam.

Scope

  1. Read the agent-commerce kernel and the truth-graph kernel end to end — the physics is non-obvious and not optional
  2. Spec the dual surface — what does the human see, what does the calling agent receive, where do they share semantics
  3. Design the human-facing surface as an Alloy component (production code, design tokens, design system rigor)
  4. Design the machine-facing surface as a structured confidence + evidence payload (JSON schema, MCP-compatible)
  5. Ship both surfaces wired into one Alloy answer in production
  6. One-page handoff doc that an integrator (a developer building on the MCP) can install from

What success looks like

  • One Alloy answer in production carries the new component on both surfaces
  • An external developer reading the handoff doc + JSON schema can install the machine-side payload in their own agent loop without re-asking
  • The human-facing component matches the trust primitives from PRJ-01 (VCI) — coherent across surfaces, not a parallel invention
  • The candidate's choices about WHICH Alloy answer to wire it into reveal strategic judgment about leverage points
  • The candidate consulted the agent-commerce kernel's Cascade Architecture before designing — visible in their reasoning

References

references.md
~/cortex/aios/kernels/agent-commerce-kernel.md — read end-to-end, especially A-1 Protocol Economics and the Cascade Architecture
~/cortex/aios/kernels/truth-graph-kernel.md — verdict primitives, evidence chain
~/cortex/aios/kernels/productai-kernel.md — A-2 Three Knowledge Domains
Alloy product surface (live) and Product.ai MCP server endpoints
Phase 2 AI Engineering axioms on agent commerce, MCP design, confidence calibration
Phase 2 Design axiom A6 — Surface-Template Alignment

Constraints

  • Claude Code or Co-work as primary substrate
  • Both surfaces must ship in production wired into one real Alloy answer
  • The machine-facing payload must be MCP-compatible (Anthropic MCP spec)
  • IP separation honored — Alloy code is in scope; aios-methods is not (this project does not require methodology access)
  • The component must align with PRJ-01 (VCI) trust primitives if VCI has shipped; if VCI ships in parallel, the candidate proposes the alignment
Apply
01

Read the Codex (10 min)

The operating principles we work by. If they resonate, the rest of this will land. Open the Codex →

02

12-minute video screen

Hireflix, async. Questions are calibrated to this project specifically.

03

Chemistry call (30-60 min)

Direct call with the CEO. Strategic alignment and mutual fit. No problem-solving exercise.

04

Project begins within 2-3 weeks

1099 contractor agreement, NDA, paid at your stated rate. Day 1 in Santa Monica.

Alpha Team members can take this project without the screen-and-call sequence. Reach out via the Alpha Team channel.