The Complide → Crux project index

Ship the useful layer. Keep the evidence attached.

This is the working map of what has been built across the repository: usable open source, the next cleanup candidates, private-preview product work, research that needs a disclosure gate, and experiments we are keeping as history rather than pretending they are active.

Living catalog

One lineage, thirty-one projects.

“Public now” means a usable artifact exists today. “Prepare next” names a bounded cleanup. Research and preview labels are deliberate: neither is a production claim.

0 matching projects

Last consolidated: August 2026 · 95 branch lineages reviewed

No project matches that search and release filter.

Fastest externalization sequence

Release coherent pieces, not the branch pile.

  1. 01 Standup package: add package metadata and a focused README.
  2. 02 Question-quality bundle: add a dataset card, schema check, and citation.
  3. 03 MCP package: merge compatibility fixtures and document each host.
  4. 04 Think skill: publish the smallest question-layer reference integration.
  5. 05 Core RC: add secret scanning, resolve dataset rights, and fix stale docs.

The release boundary

What will not appear in this public index

  • Patent strategy, provisional drafts, or claim architecture
  • Raw customer prompts, plans, answers, credentials, or traces
  • Named prospects or private partner strategy
  • Unreviewed dynamic model-control implementations
  • Concept-only mobile, glasses, or AR work presented as product

Historical project names remain visible when they explain the lineage. Sensitive implementation details do not.

The current center

Complide is the open substrate. Crux is the question layer.

The next public releases should make that relationship easier to understand: host integrations and evaluation in the open, measured private-preview workflows for the product, and explicit review gates around mechanistic research.

Test a workflow