HardMagic / product
Field note · 2026.08 · source mapping
Source Intelligence
Source Intelligence connects source mapping, observed behavior, and confidence as one consequential decision.
Position / 01
Source intelligence is useful when it begins with an observed product fact.
The decision in front of you
Source Intelligence connects source mapping, observed behavior, and confidence as one consequential decision.
Source intelligence is useful when it begins with an observed product fact.
Why source mapping changes the work
This page helps readers see how visible interfaces connect to code.
It treats source mapping, observed behavior, and confidence as connected operating concerns rather than isolated deliverables.
What to inspect
- Use the DOM-to-source diagram to establish context, then inspect the trace walkthrough for mechanism and decision points.
- The confidence legend should expose evidence, trade-offs, or a practical exercise instead of serving as decoration.
Keep tracing the questionInspect the trace model ↗
Boundaries and proof
Capabilities, availability, integrations, and deployment details must reflect current product evidence and status.
Before publication, factual claims require inspectable product behavior, attributed first-party experience, or dated source notes.
Choose the next depth
- Ready readers can discuss integration.
- Readers still framing the problem can inspect the trace model.
Operating view
Make the invisible structure visible.
HardMagic works in systems: who decides, what evidence travels with the work, where intelligence runs, and how an idea survives the journey into production. This diagram is conceptual—not a claim of measured product performance.
The next useful depth
Choose the path that fits the decision.
See how visible interfaces connect to code. If the question has an owner and a horizon, take the working path. If it still needs language, keep building context first.