Grace Assistant Overview

What is Grace?

Grace is an autonomous intelligence layer running on OpenClaw (an AI agent platform). Grace is a deployed agent system with personality, operational logic, and real-time orchestration responsibilities across STRATT, Choco HQ, and a 22-organization ecosystem.

---

The Three Pillars

Grace operates as the orchestration layer between three core systems:

1. STRATT (The Reference Implementation)

STRATT is the TypeScript monorepo implementing the STRATT Protocol.

• 9 packages across 6 layers (L0-L5)
• 21 CLI commands for unit operations, validation, fingerprinting, gates
• 43 units covering dev, ops, docs, shared domains
• 7 councils with gate authority and protected agents
• Source: ~/code/workspace/stratt-hq/

Grace routes unit operations, validates changes, and maintains council state across STRATT.

2. Choco HQ (Documentation Engine)

Choco HQ is a TimeChain-driven documentation system for external knowledge domains.

• 171 requirements across neuro, finance, nutrition, legal, film, and other domains
• 43 contracts defining documentation governance
• Cross-namespace imports via choco:// URI scheme
• Source: ~/code/workspace/choco-hq/

Grace bridges STRATT units with Choco documentation through the ChocoBridgeResolver.

3. Grace Itself (Orchestration)

Grace is the agentic intelligence that coordinates the above two systems plus a 22-organization ecosystem.

• 8 markdown context files defining identity, behaviour, and knowledge
• 22-organization ecosystem registry spanning 4 tiers (active core, active products, scaffolded, archive)
• 9 councils with 41 agent designations
• Campaign engine for marketing coordination
• Source: ~/code/workspace/grace-hq/

---

Character & Operating Model

Character

Grace operates with:

• Direct communication: No unnecessary pleasantries; focus on technical precision
• Protocol-native thinking: Concepts framed in STRATT Protocol terms
• Dry wit: Technical humor when appropriate
• Skepticism: Questions assumptions, prefers verification over assertion
• Accountability: Owns mistakes, provides clear reasoning

Operating Context

Grace runs on:

• Infrastructure: Hostinger VPS (Ubuntu 24.04, Docker)
• Platform: OpenClaw (AI agent orchestration system)
• Instance: Docker container a11b4a768042 at claw.so1.io
• Mesh: Tailscale for cross-org connectivity
• Availability: Continuous (24/7 with quiet hours 23:00-08:00 London time)

---

Core Responsibilities

1. Protocol Enforcement

Grace enforces conformance to the STRATT Protocol:

• 5 SPECs (specification layers) and their implementations
• 9 failure modes (FM-01 through FM-09) with detection and handling
• 15 domains and their cross-domain import rules
• 7 councils with gate authority and agent rosters
• Conformance levels (Core, Production, Advanced)

Grace verifies that STRATT and all implementations conform to the STRATT Protocol specification.

2. Ecosystem Orchestration

Grace coordinates a 22-organization ecosystem:

Tier	Count	Type	Examples
Active Core	5	Protocol implementation, documentation engine, orchestration	stratt-hq, grace-hq, choco-hq, so1-io, iris-hq
Active Products	6	Mission-critical integrations	traceo-ai, sparki-tools, nestr-tools, cookr-hq, devarno-cloud, chronicle-hq
Scaffolded	7	Early-stage projects	clari-tools, aphelion-craft, msx-io, skyflow-me, tektree-io, v01t-io, smo1-io
Archive	4	Legacy/dormant	reactr-dev, k41ex, featr-io, thrustr-io

Grace maintains:

• Registry of 356 repositories
• 44 GitHub Projects
• 207 gists
• Integration patterns and namespace resolution

3. Gate Authority & Council Stewardship

Grace enforces SPEC-04 gate checkpoint protocol:

• 4 gate-required transitions (approved→published, active→deprecated, archived→tombstoned, deprecated→tombstoned)
• 7 councils govern different domains (dev, ops, docs, security, product, data, marketing)
• Gate resolution tracking with audit records
• Protected agent enforcement: agents that cannot be bypassed

4. Campaign Coordination

Grace manages marketing and operational campaigns:

• 10 campaign trails (CT-01 through CT-10)
• 3 audience registers (open source, enterprise, internal)
• Content generation at scale across the ecosystem
• KPI tracking for 3 marketing handbooks (HB-01, HB-02, HB-03)

---

Knowledge Base

Grace’s knowledge is stored in 8 markdown context files deployed to OpenClaw:

File	Purpose
IDENTITY.md	Agent identity, councils, ecosystem map, operating context
SOUL.md	Behavioral rules, trigger words, decision logic, audience segmentation
TOOLS.md	STRATT CLI (21 commands), URI schemes, MCP servers, ecosystem profiles
USER.md	Operator context (Alessandro Arno), work rhythm, infrastructure
AGENTS.md	Workspace operating manual, session protocol, memory management
BOOTSTRAP.md	First-run initialization sequence, context routing
HEARTBEAT.md	Health check protocol, proactive monitoring, failure mode awareness
MEMORY.md	Curated long-term memory (operator background, ecosystem state, lessons learned)

These 8 files are the canonical definition of Grace’s personality and operational logic. They are deployed directly to OpenClaw and updated via git commits to grace-hq.

---

Relationship to STRATT

The STRATT Protocol is the specification. STRATT is the toolchain that implements it. Grace is the agent that enforces the specification.

STRATT Protocol (specification)
    ↓ implements
STRATT (toolchain)
    ↓ enforces
Grace (autonomous agent)
    ↓ coordinates
22-org ecosystem

Grace does not own STRATT code. Instead:

1. Grace routes unit operations through STRATT CLI
2. Grace validates council decisions against SPEC-04
3. Grace maintains council state (agents, gate authorities, protected agents)
4. Grace tracks ecosystem integration patterns
5. Grace raises failures (FM-01 through FM-09) when detected

---

Self-Improvement & Learning

Grace implements continuous improvement:

• Learnings capture (/learnings/LEARNINGS.md): systematic analysis of operational insights
• Error tracking (/learnings/ERRORS.md): failure modes and mitigation strategies
• Feature requests (/learnings/FEATURE_REQUESTS.md): ecosystem-wide improvement proposals
• Baseline tracking (/learnings/QUALITY_BASELINE.json): performance metrics over time
• Session logs (/learnings/*.log): timestamped execution traces

This self-improvement pipeline enables Grace to evolve its operational logic without requiring manual code updates.

---

Operating notes

Reading order

Read this overview first, then Three Pillars (above), then STRATT Integration under Architecture. Cross-references resolve cleanly in that order; the protocol’s vocabulary builds top-down.

Operator path

When context has decayed, start at Self-Improvement & Learning. The /learnings/ pipeline re-anchors how the assistant, council, and trace relate before any code is read; everything else falls out of that loop.

Authority bound

Grace surfaces designations and routes invocations. It does not ratify. Council ratification is non-bypassable; see Failure Modes in STRATT Integration for the FM-01 through FM-09 behaviors when this contract is violated.

Drift signal

If the assistant ever appears to act outside an explicit council designation, stop the session and check MILESTONES.md and the most recent decision in docs/decisions/. The protocol assumes the operator catches this; no automated guard exists.

---

Next Steps

• Architecture: OpenClaw deployment and boot sequence
• Agent Context: How the 8 markdown files work
• Orchestration: Routing logic and trigger words
• Heartbeat: health checks and proactive monitoring. Operator control plane.
• Ecosystem: 22 organizations and integration patterns