MYR — Methodological Yield Reports

A pistis-native intelligence compounding system. Every meaningful OODA cycle (Observe, Orient, Decide, Act) produces yield — techniques, insights, falsifications, patterns. MYR captures it cryptographically signed so it compounds across sessions, agents, and nodes.

Repo: https://github.com/JordanGreenhall/myr-system

Required Outputs

For every MYR operation, return:

1. 1. Action performed
2. Artifact IDs affected
3. Verification result
4. Next recommended step

Installation (New Node)

One-step install (recommended)

CODEBLOCK0

This clones the repo, installs dependencies, generates your keypair, prompts for a node ID, runs the five-command ping test, and adds MYR_HOME to your shell. Node is operational when it completes.

If you already have the repo cloned:

CODEBLOCK1

Manual install

CODEBLOCK2

Edit config.json:

• - Set unique node_id (short, e.g. n2, north-star) — must not be n1
• Set port (default: 3719, choose any open port)
• Set node_url to your externally reachable address (Tailscale IP recommended — see Network section)
• Confirm paths and key locations are writable

Generate keys:

CODEBLOCK3

Set environment:

CODEBLOCK4

Node Identity

Every node must have a unique node_id and a node_uuid. These are set during keygen and enforced at runtime.

All scripts refuse to run if node_id is still the default "n1". You will get an error with remediation steps and exit 1.

INLINECODE12 generates your keypair and writes node_uuid to config.json automatically. Verify your identity:

CODEBLOCK5

Output:
CODEBLOCK6

Verify Installation (Ping Test)

Run all five. All must succeed.

CODEBLOCK7

If all five succeed, node is operational.

HTTP Server (Live Peer Sync)

MYR includes an HTTP server for live peer-to-peer synchronization. Peers sync automatically on a schedule — no manual package exchange required.

Start the server

CODEBLOCK8

Output:
CODEBLOCK9

Run as a persistent service (macOS launchd)

Create ~/Library/LaunchAgents/com.myr.server.plist:

CODEBLOCK10

CODEBLOCK11

Verify:
CODEBLOCK12

Server endpoints

Network reachability

Peers must be able to reach each other's server. Options:

• - Tailscale (recommended): Install Tailscale on both nodes, set node_url to your Tailscale IP (e.g. http://100.x.x.x:3719). Private, encrypted, no port forwarding needed.
• VPN: Any shared VPN works the same way.
• Public internet: Set node_url to your public IP/domain with port forwarding. Less recommended.

Peer Management

The bin/myr.js CLI manages live peers.

Add a peer by URL

CODEBLOCK13

This fetches the peer's discovery document, registers their public key, and sets trust to pending.

Exchange fingerprints out-of-band (required)

Before approving any peer, verify their fingerprint through a separate channel (voice, Signal, in-person):

CODEBLOCK14

Do not approve a peer without confirming fingerprints out-of-band. This is the trust anchor.

Approve or reject

CODEBLOCK15

List peers

CODEBLOCK16

Manual sync (on demand)

CODEBLOCK17

Automatic sync runs every 15 minutes for all trusted peers once the server is running.

Mark reports as shareable

Only reports explicitly marked share_network=1 are served to peers. Mark your verified reports:

CODEBLOCK18

Connecting to an Existing Peer (Full Flow)

1. 1. Start your server and confirm it's reachable at your INLINECODE29
2. Get peer's URL — their Tailscale IP and port
3. Add them: INLINECODE30
4. Exchange fingerprints out-of-band — call, Signal, in-person
5. Approve: INLINECODE31
6. Ask peer to approve you — they run the same steps from their side
7. Verify sync: node bin/myr.js sync <peer-node-id> — should return reports
8. Mark your reports shareable (see above) so peers can pull from you

Peer Verification (v1.2.0)

MYR v1.2.0 introduces in-band fingerprint verification during the announce flow. When a peer announces to your node, a 3-way check runs automatically:

1. 1. The announced fingerprint matches the fingerprint computed from the announced public key.
2. The peer's discovery document is fetched from their URL.
3. The discovery document fingerprint matches both the announced and computed fingerprints.

Peers passing all three checks are marked verified-pending-approval. Peers failing any check are rejected with evidence stored for audit.

Verify a remote peer (CLI)

CODEBLOCK19

Returns verified status, operator name, fingerprint, and latency. Exit code 1 on failure.

Announce to a peer

When adding a peer with myr peer add --url <url>, MYR fetches the peer's discovery document and sends an introduce request. In v1.2.0, the announce body includes fingerprint, node_uuid, and protocol_version fields for in-band verification.

Auto-approve verified peers

Set auto_approve_verified_peers: true in your node config (~/.myr/config.json or config.json) to automatically trust peers that pass 3-way fingerprint verification:

CODEBLOCK20

When enabled:

• - Peers announcing with protocol version ≥ auto_approve_min_protocol_version (default 1.2.0) that pass 3-way verification are immediately trusted.
• A reciprocal announce is sent automatically so both sides can establish trust in a single round-trip.
• The auto_approved flag is recorded in the peer record for audit.

Security note: Only enable auto-approve on nodes where you trust the network environment. On untrusted networks, keep manual approval (auto_approve_verified_peers: false, the default) and verify fingerprints out-of-band.

Capturing Yield

CODEBLOCK21

Yield types:

• - technique — reusable method that works
• INLINECODE47 — orientation-changing understanding
• INLINECODE48 — proof something does not work (high value)
• INLINECODE49 — recurring structure across cycles

Searching Prior Yield

CODEBLOCK22

Use before known-domain work, architecture decisions, and when asked "what do we know about X?"

Verification and Rating Policy

• - Rating scale is 1–5.
• Only designated operators may assign final ratings.
• A MYR is "network-eligible" only after at least 1 operator review with rating ≥ 3.
• Node join criterion: at least 10 MYRs, average operator rating ≥ 3.0 over the most recent 10 reviewed MYRs.

CODEBLOCK23

Weekly Digest

CODEBLOCK24

Manual Package Exchange (Alternative to Live Sync)

If live server sync is not available, export/import signed packages manually.

Export

CODEBLOCK25

Produces signed JSON in $MYR_HOME/exports/.

Import

CODEBLOCK26

Import errors:

• - "You are importing your own artifacts" — nodeid and nodeuuid match your node. Exit 2.
• INLINECODE52 — nodeid matches but nodeuuid differs. Peer must set a unique node_id and re-export. Exit 2.
• Key mismatch: import exits 3 with remediation. No silent key overwrite.

Cross-Node Synthesis

CODEBLOCK27

Identifies convergent findings, divergences, and unique contributions across nodes.

Signing and Trust Requirements

• - Every exported MYR bundle must include a detached signature and signer ID.
• Import must fail closed on signature verification failure.
• Never merge unsigned or unverifiable MYRs into trusted datasets.

Memory-System Integration (Async)

• - MYR capture must be fire-and-forget from the primary agent flow.
• Do not block user response on MYR persistence.
• On persistence failure, log the error and surface a non-fatal warning.

ID Format

INLINECODE53 — example: INLINECODE54

Architecture

For network protocol and scale roadmap, see:
INLINECODE55