Creative production, carried forward. Explore the model, the tools and how their parts connect.
These paths connect the concepts to concrete work. Each step labels what is available, what uses demonstration data and where a handoff is still proposed. They are examples of the direction, rather than promises of a fully integrated pipeline.
A map of available local steps and intended handoffs; the complete path is not integrated.
Keep the original thought available before organizing it.
Available: Manual paste/text-file intake and hooks for already-produced Scan files preserve originals and a reviewable text proposal.
Boundary: TXTX/FSNotes evolution is a broader direction; capture does not automatically make a project or task.
Available locallyReview wording, structure and unresolved placement.
Available: A deterministic SPAR host can propose normalized Markdown with the received original and a diff; selected-item integration is tested with fixtures.
Boundary: This is deterministic text handling, not general handwriting understanding or automatic graph reasoning.
Local capability + fixture integrationSeparate “ready to inspect” from an accepted production change.
Available: MEAL/DING local profiles keep a candidate revision, comments and review intent together.
Boundary: The intake item is not automatically dispatched into MEAL or applied to a real production.
Local prototype; handoff proposedIdentify where the title card belongs without inventing a destination.
Available: The model distinguishes project context, production and identity-bearing components.
Boundary: A complete intake-to-project writer is not connected; a readable address alone does not resolve a real target.
Project / production / product · JANK
Proposed handoffExplore the title, controls and project view in an isolated working document.
Available: AE0N fixture editing, references, saved views and some native interactions have been exercised.
Boundary: Native acceptance is partial; further interaction/recovery acceptance is still needed. It is not yet a reliable production editor.
Prototype with partial native acceptanceKeep a primary preview separate from a delivered or operating endpoint.
Available: Local fixture previews and explicit collection plans can be inspected.
Boundary: A preview is not a finished render; this walkthrough does not publish a .LIVE endpoint. Renderer conformance and publishing remain separate work.
TLJ_ / HERO / .LIVE · Collect → commit → publish
Fixture preview; live delivery proposedVerified data and filesystem rehearsal using demonstrations and labelled placeholders.
Choose a bounded example instead of treating every scaffold as finished work.
Available: BLNK contains curated workflow scenarios, including a graphics package, alongside unfinished scaffolds.
Boundary: Example documents and scaffolds are not completed products.
Available fixtureKeep identities, relationships and source lineage in a compact representation.
Available: The materializer reads a data-only test snapshot derived from the authored BLNK documents and can resolve known names or IDs.
Boundary: This bounded lite profile is not a universal XDHD format or a complete media package.
Verified local profileSee titles, records, workflow and dependencies before generating files.
Available: A plan and readable preview show the proposed local tree and customizations.
Boundary: Human labels and paths are projections; they do not replace stable object identity.
Materialize / Scaffolder · pr0j.base
Verified local planningProduce useful files while retaining the source.
Available: The pipeline creates project documents, object records, guides, manifests and visibly labelled SVG placeholders, then records output hashes.
Boundary: No media renderer runs; placeholders are not faithful artwork, video or finished HERO assets.
Verified local derivationCheck provenance and inspect generated project data without pretending it is a completed render.
Available: Rerun and comparison behavior preserve source lineage; the generated project graph can be inspected by a compatible bounded loader.
Boundary: A loader check is not native visual acceptance. Shared-owner installation and general heavy-resource packaging remain pending.
Materialize / Scaffolder · AE0N / .CORE / .MacApp
Verified data compatibility; native acceptance limitedLocal planning is implemented; automatic schedule-to-playout delivery is not connected.
Distinguish a deadline, planned day and scheduled programme interval.
Available: YEAR projects date-only, all-day and timed records; TimeLine can present those records in shared views.
Boundary: These views do not create a connected calendar account or change the source records.
Verified local projectionTurn an explicit weekly recipe into planned occurrences.
Available: 365.25 supports bounded once, daily and weekly recipes and expands them into planned occurrences.
Boundary: Fixture planning is separate from actual broadcast history.
Available local planning + fixture dataFind overlaps and declarations that need review.
Available: Local UI, CLI and validation API report schedule conflicts, missing media and unfilled time.
Boundary: Asset lengths and rights are declarations; this step does not independently decode or clear the media.
Verified local validationPin the version being reviewed.
Available: The local release rehearsal records plan and asset hashes and produces a reviewable export.
Boundary: Dispatch is not attempted; an export does not update a station queue.
365.25 / M1ND.365.25 · MEAL / DING
Local rehearsalUse the current player while keeping actual playback separate from the plan.
Available: Intentional Play can start an external radio stream with m0sh visuals.
Boundary: The plan above does not drive that stream, and playback here is not a complete actual-playout ledger.
Available runtime; planning handoff proposedPut clocks, date notes, drawing and listening on a studio screen.
Available: The browser-based board prototype supplies those views with local persistence and exports.
Boundary: Its notes are not the programme master; connected calendars, shared presence and multiuser state remain future work.
Browser-local capability; shared integration proposedA local album fixture and collection rehearsal, not an uploaded release or embedded production-audio engine.
Start with music-focused vocabulary and useful defaults.
Available: Trusted profile records supply artist, album, track, artwork, video and collaboration workflow descriptions.
Boundary: Choosing a profile does not import the artist library or port every SRZA engine into AE0N.
Available prototype profileGive the demo an artist name, title and four tracks.
Available: The local scaffold supports an explicit bounded track count and offline-WIP or retained-work-feed lifetime.
Boundary: The generated graph is demonstration data, not a new release in a live catalog.
AE0N / .CORE / .MacApp · Project / production / product
Verified local fixture creationKeep the album structure and proposed deliverables visible together.
Available: The fixture carries track placeholders, artwork/video workflow steps and saved project views.
Boundary: Audio processing, complete artwork generation and external tools need their own implemented adapters.
Fixture workflow; broader engines pendingKeep unfinished work local until collection is useful.
Available: Saved storage intent distinguishes retained local WIP, retained work feed and fixture collection.
Boundary: Retained work feed is not automatic deletion or publication.
FNDR / Desktop / work.feed · Collect → commit → publish
Available local intent modelMake copy/reference choices and inspect missing resources before a snapshot.
Available: The fixture engine plans a declared dependency closure and can create an explicit local collection with a receipt.
Boundary: Referenced assets make a collection non-self-contained. The native loader does not yet automatically relink media from that collection manifest.
Verified fixture engine; native execution unverifiedTreat catalog commitment and public release as separate milestones.
Available: The prototype retains the proposal and source lineage for later review.
Boundary: No canonical catalog write, release upload or public publishing occurs in this example. Album and collaboration naming mappings remain open.
Collect → commit → publish · TLJ_ / HERO / .LIVE
Proposed production handoffAn AE0N demonstration of the architecture; complete cross-platform parity is still a direction.
Separate production records from the interface that displays them.
Available: Existing modules provide reusable validation, identity-aware records and bounded transformations.
Boundary: CORE extraction is incremental; the whole system is not already host-independent.
Implemented modules within draft architectureUse the platform for file selection, windows, input and rendering only where supported.
Available: The Mac prototype hosts a bounded document loader, saved views and supported controls.
Boundary: A capability name is not proof of an implemented adapter, and the Mac demonstration does not establish Linux parity.
XDHD.CORE / XDHD.HOST · AE0N / .CORE / .MacApp
Available Mac prototype; parity proposedInspect properties while keeping the same panel and production object.
Available: The native demonstration exercised individual/global front-back sides and shared values.
Boundary: Some editing and recovery interactions remain experimental.
Partially accepted native behaviorSee where a title or accent comes from and how an explicit override differs.
Available: Same-project fixture references, inheritance, override and reset have local/native evidence.
Boundary: A visible reference is not a commerce connection, arbitrary effect implementation or completed drag-pickwhip tool.
Available fixture bindingUse an authored production view and a compact companion without changing the project identity.
Available: Named presets, a saved laptop variant and resizing were exercised; the authored target remained intact.
Boundary: The compact companion is a read-only review preview. Physical-display detection and every recovery case are not accepted.
Partially accepted native layout behaviorReuse supported contracts instead of assuming every panel can run everywhere.
Available: Loader contracts preserve identities, unknown fields and declared supported behavior across consumers.
Boundary: AE0N panel RACK is distinct from the physical rack/inventory domain also named RACK.CORE. Neither implies universal host or renderer parity.
Architectural direction with bounded contracts/ search · Esc reset. “Related terms only” shows a term and its immediate connections.
48 of 48 terms
No matching terms. Try a broader phrase or choose “Show all”.
Model + ecosystem
An open creative-production model for giving material identity, relationships and a path from capture to composed and live outcomes.
Knowledge + specification
The working specification and knowledge collection, preserving distinctions between concepts, implementation profiles and evidence.
Native application
The native Mac home for creative tools, local cartridges and media workflows.
Studio environment + offer
The production environment connecting persistent media, compute, lightweight authoring and public services.
Shared working environment
The common production shell and host-profile direction: shared data and commands, adapted to each machine.
Architecture + modules
CORE carries reusable models, commands and transformations; HOST exposes the capabilities a particular platform can actually supply.
Interface system
The shared house-interface lineage used by XDHD.OS, SRZA.OS and BLNK.OS flavours.
House workflow profile
A trusted house UI style plus useful default workflows and launchers.
Views + capability lenses
Task-specific views over one production: BRND, STYL, UIUX, GFXR craft/workflow, FAFH file/folder references, LENS camera-and-grip, PR0J/PR0D/PR0C, EDIT, CHNL, 24HR, CREW, S0NA and MRKT.
Working contexts
Scoped creative contexts sharing graph concepts while retaining explicit identity, permissions and membership.
Demo context + fixtures
The common demonstration lineage, with examples used to test authoring and production flows.
Identity + addressing
Stable addressability for production objects, with readable expressions pointing to identity-bearing records.
Roots + endpoints
TLJ means Top Level JANK. HERO names a preferred primary visual/endpoint; .LIVE marks external delivery or operation.
Working vocabulary
PR0J establishes owned project context; PR0D is the actual production; a product is an outcome/offer rather than an automatic folder level.
Records + compositions
CARD can be an actionable record or a static one-frame projection; COMP is the time-based or otherwise composed output.
Linked media representations
Heavy/full media and light graph, proxy or working representations linked to the same production identity.
Filesystem projection
The local filesystem/materialization organization for working contexts, projects and their representations.
Light representation
A lightweight representation of identities, relationships, manifests and activity, with references to heavier resources.
Local derivation pipeline
A derivation pipeline that turns a lightweight graph into readable local project files while retaining source identity and lineage.
Local authoring surface
Local file/item presence and retained work.feed support offline WIP before acceptance into a cartridge.
Review boundaries
Collect reviews dependencies and destination; graph commitment and public publication are later, distinct actions.
Living-project control surface
An expanded project control surface for layouts, RACKs, properties, effects, STYL and TimeLine, with native-renderer ancestry.
Front / back workspace
AE0N panels with a front for use and a back for properties, effects, STYL and reference wiring.
Authored layouts
Project-owned target layouts for Retina, larger displays and compact/web companions, with guarded save/revert and resize recovery.
Typed bindings
Same-project references and inheritance used to wire controls and fixture-driven live views.
Creative + performance engine
The existing web creative/render/performance engine and portable preset lineage.
Platform policy
XDHD supports a choice of renderers. Broader XDHD retains optional After Effects; Linux targets m0sh and portable AE0N contracts, with other engines evaluated when needed.
Commerce direction + fixtures
The commerce direction, a read-only SKU evidence registry and isolated authoring fixtures have related but distinct roles.
Artist workflow profile
Artist/album/track/artwork/video tools and defaults, including compilation and collaboration context.
Delivery package + proposal
An existing directory-package delivery family with frozen selected versions, hashes and recipient notes.
Orchestration model
Routes reasoned work toward tasks, time planning, decisions and bounded delegation.
Task-review desktop
A seven-day task-review desktop with Calendar, 365.25 and TimeLine views over supplied records.
Temporal-planning direction
The proposed time/calendar-planning destination in the current DDDD model.
Ordered review
MEAL means Move Everything Along: an ordered review checkpoint. DING marks an exact candidate revision ready for review.
Dates + calendar projection
A shared foundation distinguishing planned days, deadlines, all-day ranges, timed intervals and undated work.
Unified source views
Human-and-agent-readable capture, recall, planning and reference views over original records.
Annual programming
Shared annual calendar/programme assembly; M1ND.365.25 is a configured client, not a forked app.
Player + runtime
The radio/listener/runtime lineage, paired with programming tools and m0sh visuals.
Ambient studio board
An ambient studio board with clocks, date notes, pins, whiteboard, countdown, radio and m0sh views.
Assistant direction
Studio Personal Assistant and Runner/Renderer: source-grounded assistance, preparation and bounded execution.
Canonical local intake
The intake layer above paste/drop and Scan, preserving originals, provenance, extraction and reviewed normalization proposals.
Text authoring lineage
Low-friction human-readable notes and authoring for capture, Dispatch and decisions.
Physical-to-graph workflow
Handwritten 4×6 card → preserved capture → reviewed interpretation → staged graph → traceable reverse label.
Acquisition routes
First-class card-photo and scanner-export intake with boundary/orientation review and derivative/OCR provenance.
Native wrapper foundation
A reusable manifest, policy and native-wrapper foundation for web content presented as focused app windows.
Build family
A stripped-down Linux family reusing real CORE/store/navigation/cartridge contracts and m0sh through host profiles.
Purpose-built profile
A control-room profile for camera ingest, routing, recording, confidence views and separate m0sh program output.
Dedicated-machine concept
A focused machine that runs m0sh visuals and, where qualified, contributes capture/control to a production.
XDHD is an open creative-production model. XDHD.Pro, XDHD.OS and the other components realize parts of that model through particular interfaces and hosts. An open specification and a commercial implementation have different roles.
This edition explains purpose and relationships. “Draft model” marks developing semantics; “Prototype” marks bounded experimental behavior; “In development” marks implemented work with a developing scope; “Proposed profile” marks a machine or workflow direction requiring qualification. No label implies universal compatibility or production acceptance.
Examples preserve the distinction between a note, a review proposal, an accepted record, a composed artifact and a live endpoint. A saved preview or fixture result is not automatically a published production.
Definitions and relationships come from one editable entry graph. This public edition includes reviewed concepts and examples; operational history and source receipts remain a separate reference layer. Reviewed 2 November 2026.