Archived challenges

What’s here

Challenges that started as fresh-agent research briefs and have been resolved — meaning a deliverable was produced and Crosswalker committed to a direction in a dated log. The original brief is preserved verbatim so the same challenge can be re-run later (e.g., when external conditions change) without losing the original framing.

Each archived challenge has a top-of-file callout pointing to the resolving log entry.

Archived challenges

• Challenge 06: Pairwise vs synthetic spine

  • Resolved 2026-05-01 → Foundation commitments and follow-on research

• Challenge 07: Link metadata / edge model

  • Resolved 2026-04-10 → Evidence-link edge model synthesis

• Challenge 45: Org rollout readiness

  • Resolved 2026-08-21 → Can Crosswalker be used at work yet?

• Challenge 43: Version migration — the semantic-diff loop

  • Resolved 2026-08-27 → Release change is re-attestation

• Challenge 44: E2E testing strategy

  • Resolved 2026-08-24 → Repair determinism, then enforce

• Challenge 46: The transform engine and the shapes of data

  • Framed 2026-08-27 → Transformation has two shapes
  • Resolved 2026-08-27 → The source contract shipped

When to re-run an archived challenge

A challenge is archived as resolved, not closed. Re-run when:

• An assumption the resolution depends on changes (the resolution callout typically lists these)
• New research surfaces that contradicts the committed direction
• A fresh agent wants an independent perspective on a load-bearing decision

Active challenges

See the main challenges index for currently open briefs.