C1 System Designer — Human-Facing KERI Service Definition

Overview

Designs a human-facing service that operates within a KERI-backed ecosystem. This is the C1 level of the C4 architecture: it defines what the service does for humans, who uses it, how it makes money, and what KERI infrastructure it requires. The output is a system.yaml (machine-readable) and service-design.md (human-readable narrative).

Key principle: C1 describes services in human terms. "Identity Protection" not "witness pools." "Instant Background Checks" not "KEL validation." Push back on KERI jargon — force plain language for anything user-facing.

Prerequisites

Before starting, read all reference files in this skill:

• references/system-schema.yaml — canonical schema template with field documentation
• references/service-patterns.md — four canonical service patterns with KERI mappings
• references/c1-design-questions.md — question bank with follow-up probes
• references/service-design-template.md — output template for service narrative

Workflow

Phase 1: Discovery