BitShovel.An information workbench for the AI era
Add information中

An information workbench for the AI era

中

NETWORK · RELATIONSHIP MAP

Points become lines; lines weave a plane — that is how the network grows.

A news feed hands you isolated items. BitShovel binds noteworthy signals to stable objects: a point is one verified signal, a line is continuous tracking of the same product line, a plane is the comparison surface across peer objects. Every number below is generated from the object registry and the three-state signal store — objects going live, watch-pool, or historical all show up here as they are.

01
THE MAP · OBJECT INVENTORY

11 managed objects: 1 market, 6 model families, 4 version objects.

The registry is the network's foundation: markets define comparison planes, families are product lines, versions are the tracked objects. 4 live signals are bound to version objects today, with 0 more connection records preserved in the watch pool and history.

02
THE LINE · SAME THREAD

New versions reconnect to the old thread instead of starting an isolated card.

Every version object registers its predecessors. When a product line ships its next release, the new card links back through that relationship: prior observations, verifications, and market contrast all carry over, and the page marks the thread as reactivated. Quiet lines sink into history without disappearing — a new evidenced change on the same object wakes the thread.

  • Google Gemini Gemini 3.5 Transcribe: Live, 1 connected signal
  • OpenAI GPT GPT-5.6 Sol: Live, 1 connected signal
  • Qwen Qwen3.8-Flash-Next: Live, 1 connected signal
  • Zhipu GLM GLM-5.3-Flash: Live, 1 connected signal

03
THE PLANE · PEER COMPARISON

6 model families form the frontier-model comparison plane.

Families with live signals: Zhipu GLM (1), OpenAI GPT (1), Qwen (1), Google Gemini (1). DeepSeek and Anthropic Claude have no card yet — an empty member is itself an observation, and the seat fills as soon as qualifying evidence appears.

Every peer event carries its own badge (market contrast), strictly separated from the object's own changes: pricing and capability moves are vertical events; peer releases and benchmarks are lateral. Retirement reads both dimensions — an object must go quiet for 7 days AND its market plane must go quiet before rotation.

04
THE LIFECYCLE · ROTATION

Live, watch pool, history: retirement is management, not deletion.

Signals stay live on a 7-day rolling window; 7 days without noteworthy change moves them to the watch pool (retired), and a 30-day review sinks them into history (historical). The history store merges by id — a returning object updates its original record instead of duplicating. All three states are public endpoints.

  • Live: the three focus cards and full list on the workbench
  • Watch pool: still resolvable on the /archive index
  • History: public endpoint at /historical-signals.json
  • Object registry: public endpoint at /managed-objects.json