A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗

PackageSibling project

@magician-network/core

The trust-routing engine: trust/1 edges, the router with the veil, the consent machine, sealed introduction/1 outcomes, beacon/1 federation, grant/1, and the transport envelopes.

version unverified — no checkout to measure on 2026-10-30 · source: magician/packages/core

npm i @magician-network/core

The parser refuses; it does not guess: unknown fields, unlabeled numbers, empty provenance, and any spelling of expiry are refused — decay is derived from renewal, never accepted as input.

Portable by rule: no node: imports anywhere in core, so the browser seals and verifies identically to the CLI. The sha256 is pure TypeScript, pinned against node:crypto by test.

This page said “not on npm yet; publication is gated on the first independent adopter” until 2026-10-30, when the first run of the registry check in tests/links.test.mjs read 0.1.0 served for both Magician packages — the install line had outlived the gate it described. The line now says what the registry says.

Edge cases — each one paid for once

A declined introduction renders exactly as a path that never existed

toRequesterView collapses the two, and a test compares the objects for deep equality. A visible refusal leaks exactly the relationship data the refusal was protecting.

Nothing a person does alone moves their standing

There is a test whose whole job is proving unilateral activity moves nothing. A reward input would have to break a named test — that is the tripwire that keeps token mechanics out of trust scoring.

← Full catalog · The doctrine behind the tools · Adopt one