# Repo C Trace Ndjson Validate

> Validate Repo C/repo_c_trace NDJSON packet integrity in <PRIVATE_REPO_C>. Use when changing trace packet fields, guardian reroute behavior, or validation tooling that checks packet monotonicity and required envelope keys.

- Skill: `grtninja/repo-c-trace-ndjson-validate` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add grtninja/repo-c-trace-ndjson-validate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/grtninja/repo-c-trace-ndjson-validate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: grtninja (https://skillmd.com/u/grtninja)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/grtninja/repo-c-trace-ndjson-validate

---


# Repo C Trace NDJSON Validate

Use this skill to protect packet stream contract integrity.

## Workflow

1. Generate or capture NDJSON packet streams.
2. Validate required packet fields and monotonic packet IDs.
3. Re-check guardian decision counters when reroute logic changes.

## Scope Boundary

Use this skill for NDJSON packet envelope integrity and trace-stream monotonicity.

Do not use this skill for:

1. Policy manifest/schema conformance gates.
2. Ranking/report scoring semantics and schema compatibility.
3. Cross-repo architecture governance boundary reviews.

## Command

Run from `<PRIVATE_REPO_C>` root:

```bash
python tools/trace_validate.py <path-to-ndjson>
```

## Required Fields

- `packet_id`
- `ts_unix_ms`
- `token_id`
- `emotion_ttl`
- `kv`
- `policy`
- `trust_anchor`

## Reference

- `references/trace-contract.md`

## Loopback

If this lane is unresolved, blocked, or ambiguous:

1. Capture current evidence and failure context.
2. Route back through `$skill-hub` for chain recalculation.
3. Resume only after the updated chain returns a deterministic next step.

