content-explorer

A user interface to dig into a field of interconnected knowledge. Inspired by onco.cc the very well organized information collection about everything related to cancer.# content-explorer

A user interface to dig into a field of interconnected knowledge. Inspired by onco.cc, the very well organized information collection about everything related to cancer.

Stage: research / repository seed, not yet a working application. Reference: https://github.com/judegomila/OnCo (code MIT; OnCo corpus CC BY-NC 4.0).

Start with INTENT.md, research/OnCoDeepDive.md, architecture/ArchitectureBlueprint.md, and workplans/INDEX.md.

North-star demo

A single UI build loads either systems-thinking or software-architecture, shows the same browse/search/detail/connections experience, and needs zero edits to React components for the switch. Source references and rights follow every imported assertion.

What this archive contains

Research grounded in publicly browsable upstream files, extraction plan, normative draft contracts, two independently authored small datasets, a basic connector example, executable fixture validator, roadmap and decision records. It does not contain or claim to be a fork of upstream source. Fetch and pin upstream at implementation time. See scripts/bootstrap-upstream.sh.

Quick seed check

python3 scripts/validate_fixtures.py

Implementation start

Workplan 00 pins upstream and records code provenance; Workplan 01 establishes clean domain fixtures, Workplan 02 extracts browse/detail shell. PRs should demonstrate test-backed progress against the acceptance criteria.

OnCo comparison track

WP-07 specifies a small, pinned, authorized OnCo reference-slice test program. No actual OnCo data is included. Public fixtures remain independently authored; real-data ingestion is disabled until the relevant data rights are cleared.