Mindware

Mindware is a working vocabulary and repo scaffold for BTA: Block → beamline → Artifact.

A mind is not a vibe, a prompt, or a logo. A mind is a system that creates a beamline capable of turning all needed blocks into a final artifact.

If the artifact cannot point back to the blocks and the beamline proof of search that collapsed it, it is not an artifact yet. It is prose wearing a hard hat.

Core terms

• Block: an input unit with provenance, boundaries, and an explicit claim about what it contributes.
• Mind: an operating system for search. It selects blocks, decomposes work, runs subminds, applies negative feedback, and records the beamline.
• Submind: a specialized mind inside a larger mind. Use as many as the artifact requires: research, critique, implementation, distribution, compliance, measurement.
• Beamline: the ordered search process that transforms blocks into candidates, criticisms, revisions, and final collapse.
• Proof of search: the receipt trail showing what was tried, what failed, what changed, and why the final artifact earned selection.
• Artifact: a crystallized view of a collection of blocks collapsed from a beamline proof of search.

BTA workflow

1. Declare the intended artifact.
2. Register the starting blocks.
3. Instantiate the mind and any subminds.
4. Run the beamline: transform, critique, revise, measure.
5. Maintain proof of search receipts.
6. Collapse the candidate set into the artifact.
7. Publish the artifact with provenance links back to blocks and beamline receipts.

Repository layout

blocks/       source block definitions and examples
minds/        mind and submind definitions
beamlines/    beamline run plans and logs
artifacts/    final artifact manifests and outputs
receipts/     proof-of-search receipts
schemas/      JSON Schemas for machine-readable manifests
specs/        conceptual protocol specs
templates/    starter manifests for new runs
tools/        validators and utilities
examples/     worked BTA examples

Minimal run

python3 tools/validate_bta.py examples/minimal-bta-run.json

Expected result:

valid: examples/minimal-bta-run.json

Plug-in toolboxes

Mindware supplies the BTA artifact pipeline: blocks, minds, beamlines, proof of search, and collapse decisions.

Reusable epistemic instruments live in separate toolboxes so this repo stays a protocol scaffold instead of becoming a drawer full of tools.

• Epistemic Toolbox: concept/reference/claim measurement tools, including paper concept-equivalence receipts. https://github.com/Marvin-The-Bodega-Cat/epistemic-toolbox

Mindware:          artifact pipeline
Epistemic Toolbox: concept/reference/claim measurement tools

Why this matters

Creative work usually hides the search and displays only the polished result. That makes feedback illegible and ownership arguments sentimental.

BTA makes the search visible:

• what blocks mattered;
• which minds touched them;
• what negative feedback changed;
• what candidate artifacts died;
• why this artifact was collapsed.

The thesis means nothing without the artifact. The artifact means little without the beamline.