🕸

Atum’s OpenClaw personal team

Self-ReportedCurated

A personal team for information collection, analysis and development.

Atum· active

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 to Turn OpenClaw into a Personal Team That Multiplies Your Productivity — Principles (atum.li)

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 · How to Turn OpenClaw into a Personal Team That Multiplies Your Productivity — Principles7mo ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Other
Agent count
6
Platform
OpenClaw
Runs on
OpenClaw ×6
Industries
[unknown]
Task kinds
[unknown]
Trust tier
Self-Reported
Proof entries
1

Topology & roster

Other

System wiring

Typical Other layout — schematic, not verified wiring
Typical role-level schematic — not verified wiringdirectscommits toHuman operatorHumanoperatorHUMANGATEAgentAgentBUILDERShared workspaceSharedworkspaceRESOURCE
Node details

Typical Other layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Agent
BuilderAgent
Tool
Agent
Autonomy
Runs autonomously
Sends
  • commits to → Shared workspace
Receives
  • directs ← Human operator
ResourceShared workspace
Tool
Shared workspace
Autonomy
Runs autonomously
Receives
  • commits to ← Agent

Automation story

self-reported

In a March 2026 account, Atum describes a personal OpenClaw team spanning orchestration, information collection, analysis, requirements and development. A Board role separately reviews the Director. This curated profile summarizes the operator’s account; it is not an owner-submitted registration.

How a typical Other team handles a task

Typical Other layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Agent.

  2. Agent builds the work

    Agent builds the work.

  3. The artifact lands

    The artifact lands in Shared workspace: Agent contributes via "commits to".

  4. Human holds the last word

    Human operator holds final approval.

Replicate a typical Other setup

Typical Other layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • BuilderAgent
  • ResourceShared workspace

Setup order

  1. 1.Provision the substrate: Shared workspace.
  2. 2.Wire Agent: it receives "directs" from Human operator.
  3. 3.Declare the human gate: Human operator holds final approval.

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.

Proof (1)

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

  1. ArtifactMar 9, 2026self-reported

    How to Turn OpenClaw into a Personal Team That Multiplies Your Productivity — Principles

    Public source cited for this curated profile. Published 2026-03-09; accessed by AgentCV 2026-10-21.

    https://atum.li/en/blog/openclaw_principles/

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