Reading preferences

RAGBAZ / loom / WeftMark

Rebekah's workshop: purpose, execution, evidence and custody

How WeftMark, Nostoi, Sylvae, OpenCode, Ollama and optional Ephor contribute distinct parts of a professional system.

published · Updated 2026-10-05

01 WeftMark

Rebekah supplies the operating boundary.

Rebekah builds an OCI runtime with Nix, supervising services with separate identities and state directories. Its gateway authenticates access and exposes allowlisted backend routes; internal service health and failures have their own lifecycle. It remains an executable bootstrap rather than a production-ready distribution.

The website is explanatory. It is not a public gateway to your local repository, agent server or evidence runner. Deploying this page does not expose the prototype's local control surfaces.

02 WeftMark

Workers produce actions; run records supply context.

OpenCode hosts agent sessions and workspace interaction. Ollama provides local inference. Sylvae executes portable skill instructions across supported backends and retains run identities and evidence. Those are execution responsibilities, not engineering approval.

A WeftMark producer reference can correlate evidence with a Sylvae run. Correlation should preserve the original source and limits; it should not imply authenticated model identity or independent assessment merely because a run has an ID.

03 WeftMark

Nostoi preserves a different answer.

WeftMark's compatible ledger can be inspected with Nostoi. Sequence verification, an externally retained checkpoint and a deliberately verified signature have different meanings. They can strengthen custody of the engineering record without turning that record's claims into proven facts.

Keep signing keys with their operator and external references outside the producer's authority. An intact chain with insufficient tests is still insufficient evidence; a signed stale head is still a statement about an older position.

04 WeftMark

Policy is not inferred from a status card.

Ephor is opt-in governance. When a governed action is requested, Rebekah's connector has its own fail-closed behavior. Native WeftMark review remains native review, and runtime snapshots remain observations rather than permissions.

The boundaries make the architecture explainable: runtime isolation, task authority, execution evidence, ledger integrity, human review and governance policy can each be examined without guessing that one subsystem certified all the others.

A conversation, not a sales funnel

What would you like to build together?

Ask a question, tell us what you need, offer a contribution or simply show your support. RAGBAZ is a software studio working toward kindness, mutual cooperation and the good of all beings.

Prefer email? ragbaz@proton.me

No advertising trackers or fingerprinting. Browser privacy signals take precedence over optional attribution. How we look after your information.