Intelligence compounds. Evidence must keep up.
Every new model, prompt, harness, and tool multiplies the number of possible systems. ProjectH turns that explosion into a navigable, verified path.
The 3D field could not initialize.The capability map remains available as structured evidence and accessible data.
| Renderer property | Value |
|---|---|
| Recursive order | Three |
| Curve vertices | 4,096 |
| Spatial dimensions | Three |
A capability profile,
with its evidence boundary.
This profile traces one published release across seven capability categories. Select a model, open an axis, or enter the lab to see the source evidence behind the shape.
Compare selected models ↗ Social Vibes for this model ↗
Axis LensClick a capability label to inspect, include, or reweight the benchmark inputs behind this displayed reading.
Evidence boundary
This view reflects a published source release. ProjectH scoring, ranking, and deployment verification remain separate qualification steps.
A score becomes useful when you can trace what produced it.
ProjectH keeps the published result, the system it describes, and every unresolved qualification visible in one reading.
- Published
Read the source record
Preserve the reported value, source revision, retrieval date, and original category boundary.
- Checked
Resolve what was evaluated
Separate a marketing model name from deployment identity, reasoning mode, harness, and run configuration.
- Qualified
Publish with limits intact
Keep missing evidence unknown, expose compatibility and freshness, and retain the path back to every visible value.
A rank answers who placed first. A profile asks whether the result applies.
- Leaderboard
- Published result and relative position.
- ProjectH profile
- Release identity, configuration, grading method, freshness, and unresolved checks.
One evidence record, read from three decisions.
A visible number keeps its receipt.
ProjectH separates observed source evidence from qualification. Missing required evidence remains unknown; old snapshots are not silently rewritten; comparison uses one compatible measurement contract.
Private profiles will open with a published scope, response owner, and data-handling terms. Until then, the public method and source view remain fully inspectable.
See the current boundary ↗