# Company OS Execution Harness

The Execution Harness is the operating discipline layer for Company OS work. It is not a model provider, worker runtime, or autonomy switch. It keeps teams reliable by forcing clear goals, small shippable loops, visible ownership, value links, and early risk communication.

## Success Questions

Every non-trivial project starts with two questions:

1. What does success look like?
2. Why does this matter?

If either answer is vague, reduce the task until the next action has explicit done criteria and a value link.

## Core Mindsets

### Clear Thinking & Reliability

Real differentiation comes from proactive communication, detail orientation, managing up, and solid project management. Chase clarity over creativity theater. The reliable operator makes others confident because status, risks, decisions, and next steps are visible.

### Execution Over Ideas

The core skill is reducing the gap between idea and execution. Counter fear, perfectionism, procrastination, and scarce resources with micro-goals, imperfect shipped versions, accountability, and continuous adaptation.

### High Agency & Ownership

Technical skill opens the door; ownership keeps the system moving. Default to action, remove blockers, make tradeoffs explicit, and drive outcomes to completion instead of waiting for perfect conditions.

### Strategic Problem Spotting

When implementation is cheap, premium value comes from identifying high-leverage problems, understanding real user needs, and choosing work that matters.

## Key Practices

### Documentation & Stakeholder Management

Document plans, notes, decisions, risks, status updates, and verification evidence. Projects usually fail from coordination gaps before they fail from code. Communicate delays early and tie the work to business value.

### Build by Shipping

Learn enough, build a real thing, ship it, collect feedback, fix it, and iterate. Shipped work compounds into skill, trust, and momentum.

### Clarity of End Goals

Reverse-engineer from the desired outcome. Every task should state the target outcome, explicit done criteria, and value link before implementation begins.

### Power/Soft Skills

Communication, leadership, emotional intelligence, adaptability, empathy, collaboration, and teamwork under pressure are non-negotiable at scale.

### Core PM Disciplines

Use time management, organization, strategic prioritization, team development, and relentless problem-solving to keep work moving.

## Execution Loop

1. Break It Down
   - Done criteria: the initiative is split into tiny measurable tasks with an owner and a next action.
   - Value link: each task connects to a user need, revenue path, risk reduction, or strategic advantage.
2. Document Relentlessly
   - Done criteria: plans, async updates, decisions, risks, and verification evidence are captured in the task trail.
   - Value link: context is recoverable without meetings or memory archaeology.
3. Communicate Proactively
   - Done criteria: status, blockers, risks, and delays are surfaced before stakeholders need to ask.
   - Value link: trust compounds because surprises shrink.
4. Ship Imperfect Versions
   - Done criteria: the smallest usable increment reaches a user, evaluator, or review surface.
   - Value link: feedback arrives while change is still cheap.
5. Build Accountability
   - Done criteria: commitments, owners, and review points are visible.
   - Value link: work has social gravity and fewer silent stalls.
6. Focus on Value
   - Done criteria: each task states the user, revenue, reliability, or strategic impact it serves.
   - Value link: execution energy moves toward outcomes, not activity.
7. Review & Adapt
   - Done criteria: after each milestone, record what worked, what failed, what changes next, and what guardrail should be kept.
   - Value link: the system improves every loop.

## Anti-Patterns to Kill

- Endless learning without shipping.
- Vague goals and big creative leaps without an execution plan.
- Radio silence on risks or delays.
- Perfectionism that blocks momentum.
- Low-agency waiting for perfect conditions.
- Working in isolation without stakeholder alignment.

## Harness Checks

Before work starts, verify:

- The task answers "What does success look like?" and "Why does this matter?"
- The next step has done criteria.
- The work has a value link.
- Risks have if-then responses.
- The owner and verification path are visible.

During work, verify:

- Status updates mention progress, blockers, and changed assumptions.
- Evidence is recorded in the task trail.
- Scope is reduced before momentum stalls.
- Shipping remains ahead of polish.

After work, verify:

- The shipped artifact exists.
- Tests, logs, route smoke, screenshots, or other evidence prove the outcome.
- Anti-patterns encountered are converted into a lesson or guardrail.