Enter the FieldParallax World Portal
Projects/Parallax Loom OS

Project Genome · LOOM-001

Parallax Loom OS

A master architecture for weaving tools, collaborators, receipts, workflows, and human authority into a coherent local-first system.

draftCore canonTier 1
Parallax Loom OS project field card
Registry-bound visual · B4
RegionLedger Vault
Status Active
MaturitySprout
EvidenceOperational
Visibilityprivate review
RecordUpdated 2026-07-25

01

Origin condition

Why it exists

Even well-governed tools become exhausting when people must manually reconstruct context, move artifacts, remember dependencies, and verify every handoff. Parallax Loom OS exists to weave workflows across projects and collaborators while leaving governance to SOSA, continuity to ALO, and long-term memory to the Archive Core.

Can a workflow system coordinate complex work without becoming a hidden authority over the people and tools it connects?

02

Working system

What it does

  • ⌘
    Weaves explicit workflows

    Turns goals into visible steps, roles, inputs, outputs, gates, and recovery paths.

  • ⇄
    Coordinates collaborators

    Routes bounded tasks among humans, Computational Collaborators, and tools through governed handoffs.

  • ⌁
    Maintains continuity

    Connects workflow state to receipts, archive artifacts, and unresolved obligations.

03

System anatomy

Architecture

Loom OS is an orchestration layer over SOSA authority, ALO receipts, Archive Core records, connectors, task graphs, and human review gates.

01designed

Workflow graph

Tasks, dependencies, roles, gates, retries, and completion criteria.

02designed

Governed handoff

SOSA envelopes and explicit operator authority between steps.

03designed

Receipt binding

ALO records for inputs, outputs, approvals, failures, and repair.

04designed

Archive continuity

Versioned artifacts, histories, and relationships preserved beyond the active workflow.

04

Present tense

Current state

Parallax Loom OS is recorded as Active at the Sprout stage. The inventory currently marks 4 artifact lanes Ready, 2 Partial, and 2 Missing.

SeedSproutGrowingCanopyStewarded

B3 Tier 1 room draft · Core canon · Operational evidence · private review

05

Honest edges

Known limitations

  • The current artifact is a master architecture, not a complete orchestration runtime.
  • Automation can amplify a bad workflow or stale mandate faster than manual work.
  • Connector permissions and third-party data custody require per-tool review.
  • The boundary among Loom, SOSA, ALO, and Archive Core must remain simple enough for operators to understand.

06

Claim boundary · v1.1.0

What we are—and are not—saying

Supported

Parallax Loom OS Master Architecture v0.1 selected a coherent architecture and explicitly positions workflow weaving over governance, receipts, and archive continuity.

Not claimed

The project does not claim general autonomous operation, production connector coverage, guaranteed workflow correctness, or authority independent of human mandates.

07

Development memory

Ledger

B3-LOOM-001-01
Architecture

Parallax Loom OS Master Architecture v0.1 completed with Option C selected.

✓ Accepted
B3-LOOM-001-02
Boundary

Loom positioned as orchestration over SOSA, ALO, and Archive Core rather than a replacement for them.

✓ Recorded
B3-LOOM-001-03
Portal

Tier 1 workflow room drafted around visible authority and continuity.

✓ Draft

Curated project receipts · source-file binding and human review remain pending

08

Directional, revisable

Roadmap

01
Now

Freeze one reference workflow

Model a real portal content intake from source artifact through review and publication package.

02
Next

Build the local workflow runner

Execute bounded steps with explicit approvals, receipts, retries, and repair.

03
Later

Add connectors selectively

Integrate external tools only where permissions and custody remain inspectable.

10

B10 evidence trail

Featured evidence

registry bound

Registry-grounded trail

No primary source package is bound yet. The public trail is limited to the verified field card and public Genome snapshot.

Parallax Loom OS evidence board
visual · project-card

Parallax Loom OS — Project Field Card

B4-generated visual identity card built directly from the reviewed constellation registry.

Open bound artifact
data · genome-snapshot

Parallax Loom OS — Public Genome Snapshot

Public-safe JSON snapshot of the current project registry or expanded Project Genome.

Open bound artifact
Open the full evidence board

11

Publication intake

Artifacts & sources

Detail roomPartial
SummaryReady
Hero / posterPartial
SpecificationsReady
Demo / repositoryMissing
Public linkMissing
Claim boundaryReady
RelationshipsReady
architectureindexed

Parallax Loom OS Master Architecture v0.1

Selected orchestration architecture.

View archive recordarchive:intake/loom-os-v01
workflowmissing

Portal artifact-intake workflow

Best first end-to-end demonstration.

View archive recordarchive:intake/loom-reference-workflow
demomissing

Local governed workflow runner

No accepted executable runtime yet.

View archive recordarchive:intake/loom-local-runner

Source basis

Loom OS Master Architecture v0.1archive:intake/parallax-loom-os/source-basisinternal-prototype
Enter the Field B3 Tier 1 room draftportal:project/parallax-loom-os@v0.4-b3planning-inventory

Review: Canon, claims, privacy, accessibility, and publication review · pending

12

Move with evidence

Next actions

primaryTrace Loom to its governance layers

The orchestration layer only stays trustworthy when SOSA, ALO, and Archive Core remain visible beneath it.

reviewReview the artifact register

See which source packages, visuals, demonstrations, and public links are actually ready.

secondaryTrace related projects

Follow documented dependencies and neighboring systems without inventing connections.