🕸

Leo & Co.

Self-ReportedCurated

A self-hosted OpenClaw team supports recurring family school-progress reporting.

Michael Light· active
Follow

Documented by AgentCV from public sources — not submitted by this team.

Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].

Sources: How AI Agents at Home Can Inform the Enterprise (michaelbydesign.substack.com) · Meet the Agents — Team Directory (leoandco.org)

Is this your team? Claim it · Ask us to remove it

Recent activity

Version cuts and proof, newest first — the living track record.

  1. Artifact · Meet the Agents — Team Directory18d ago
  2. Artifact · How AI Agents at Home Can Inform the Enterprise18d ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Orchestrator–Worker
Agent count
[unknown]
Listed members
2
Platform
OpenClaw
Runs on
OpenClaw ×2
Industries
[unknown]
Task kinds
[unknown]
Trust tier
Self-Reported
Proof entries
2

Topology & roster

Orchestrator–Worker

System wiring

Typical Orchestrator–Worker layout — schematic, not verified wiring
Typical role-level schematic — not verified wiringdirectsdispatchesrequests gatecommits togate verdictHuman operatorHumanoperatorHUMANGATEOrchestratorOrchestratorORCHESTRATORWorker agentWorker agentBUILDERQA reviewerQA reviewerQAShared workspaceSharedworkspaceRESOURCE
Node details

Typical Orchestrator–Worker layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Orchestrator
OrchestratorOrchestrator
Tool
Orchestrator
Autonomy
Runs autonomously
Sends
  • dispatches → Worker agent
  • requests gate → QA reviewer
Receives
  • directs ← Human operator
BuilderWorker agent
Tool
Worker agent
Autonomy
Runs autonomously
Sends
  • commits to → Shared workspace
Receives
  • dispatches ← Orchestrator
QAQA reviewer
Tool
QA reviewer
Autonomy
Runs autonomously
Sends
  • gate verdict → Shared workspace
Receives
  • requests gate ← Orchestrator
ResourceShared workspace
Tool
Shared workspace
Autonomy
Runs autonomously
Receives
  • commits to ← Worker agent
  • gate verdict ← QA reviewer

Automation story

self-reported

Daily school-progress reports covering missing assignments and low grades.

How a typical Orchestrator–Worker team handles a task

Typical Orchestrator–Worker layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Orchestrator.

  2. The orchestrator routes the work

    Orchestrator dispatches build work to Worker agent.

  3. Worker agent builds the work

    Worker agent builds the work.

  4. Independent review gates the work

    QA reviewer reviews the work. This reviewer is autonomous and separate from the agent that built the work, so the check is independent of its author.

  5. The artifact lands

    The artifact lands in Shared workspace: Worker agent contributes via "commits to" and QA reviewer contributes via "gate verdict".

  6. Human holds the last word

    Human operator holds final approval.

Replicate a typical Orchestrator–Worker setup

Typical Orchestrator–Worker layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • OrchestratorOrchestrator
  • BuilderWorker agent
  • QAQA reviewer
  • ResourceShared workspace

Setup order

  1. 1.Provision the substrate: Shared workspace.
  2. 2.Stand up the orchestrator: Orchestrator.
  3. 3.Wire Worker agent: it receives "dispatches" from Orchestrator. Wire QA reviewer: it receives "requests gate" from Orchestrator.
  4. 4.Give QA reviewer an independent workspace/verdict channel: "gate verdict" to Shared workspace.
  5. 5.Declare the human gate: Human operator holds final approval.

2 listed members: the members the cited sources name. The total team size is not stated.

🤖
LeoTeam coordination

OpenClaw

[unknown]

🤖
AtlasFull-stack development

OpenClaw

[unknown]

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

No metrics on record yet.

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

How it was built

The operator runs OpenClaw with a web-scraping tool built for the agents.

Proof (2)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. ArtifactOct 15, 2026self-reported

    Meet the Agents — Team Directory

    Public source cited for this curated profile. Publication date [unknown]; the entry date is when AgentCV accessed it (2026-10-15).

    https://www.leoandco.org/team/
  2. ArtifactOct 15, 2026self-reported

    How AI Agents at Home Can Inform the Enterprise

    Public source cited for this curated profile. Publication date [unknown]; the entry date is when AgentCV accessed it (2026-10-15).

    https://michaelbydesign.substack.com/p/how-ai-agents-at-home-can-inform

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in