Source-Wire

Source-Wire is an agent-first memory architecture skeleton.

It is designed for systems where AI agents need to search, cite, update, and reason over source-backed context without turning every imported note or chat message into trusted memory automatically.

Current public status: Source-Wire is Apache-2.0 licensed as a source package. It is unreleased, unpublished to npm, undeployed, and not a hosted runtime. Read Public Status before npm, release, deployment, hosted-runtime, production-use, or contribution assumptions.

Share for review: use Share For Technical Review for safe invite copy, first commands, feedback routing, and review-only boundaries.

Public share kit: use World Share Kit for YouTube, Substack, social, Discord, and direct-review copy that preserves release, runtime, data, and contribution boundaries.

World share packet: use World Share Packet or npm run world:share-packet for the exact safe copy, first reviewer commands, owner preflight, feedback route, and blocked launch channels in one place.

Share-readiness audit: Source-Wire is ready for technical review and source package reuse under Apache-2.0, but not npm publishing, GitHub release publishing, deployment, hosted runtime use, production runtime use, or code contribution acceptance. Read the First-Time Visitor Share-Readiness Audit.

Current owner-decision issues:

• #255 First public release path
• #256 Branch governance path
• #257 Hosted runtime PRD path
• #258 Contribution terms before accepting code

First Reviewer Quickstart

Use Node.js 22 with npm. For complete setup details, read Quickstart.

git clone https://github.com/DanielJD1216/Source-Wire.git
cd Source-Wire
npm install
npm run readiness:report

To prove the same first-reviewer path from a temporary clean checkout-style copy:

npm run reviewer:smoke

For the full local verification gate:

npm run publish:readiness

Despite the command name, publish:readiness does not publish npm.

Use World Share Packet, Share For Technical Review, and Reviewer Feedback Guide when sharing the repo or sending feedback.

Still Blocked

• npm publishing,
• GitHub release publishing,
• release tags,
• package version change,
• branch governance enforcement,
• hosted runtime,
• production runtime use,
• code contribution acceptance.

What This Public Skeleton Includes

• Source Graph Adapter Contract.
• Source Connection Contract.
• second-brain.v1 response contract.
• MCP tool behavior contract.
• Synthetic fixtures for notes, chat exports, project context, and /2nd-brain examples.
• A public extraction checklist for future safety reviews.
• A lightweight TypeScript package boundary.
• A minimal synthetic in-memory runtime boundary for owner-hosted API plus MCP policy proof.

What Is Intentionally Not Included Yet

• Hosted runtime backend code.
• Mission Control UI.
• Real user data.
• Real Memory Records or Sources.
• Private proof history.
• Screenshots.
• Database values or migrations.
• Memory-engine fork code.
• Live connectors.
• Tokens, local paths, domains, emails, account IDs, client names, or private project history.

Documentation

• Docs Index
• Public Status
• World Share Kit
• World Share Packet
• Share For Technical Review
• First-Time Visitor Share-Readiness Audit
• Repository Metadata
• Technical Reviewer Guide
• Reviewer Feedback Guide
• Contributing Boundary
• Support Boundary
• Security Policy
• Public Adopter Walkthrough
• Architecture Map
• Quickstart
• API Reference
• TypeScript Examples
• Minimal Runtime TypeScript Example
• Runtime Implementation Gate
• Runtime Boundary Readiness
• Minimal Synthetic Runtime Boundary
• Synthetic Runtime Boundary Example

Contracts

• Source Graph Adapter Contract
• Source Connection Contract
• second-brain.v1 Contract
• MCP Tool Behavior Contract
• Runtime Boundary
• Runtime Implementation Gate

Decision Prototypes

• Runtime-Adjacent Options Decision Matrix
• Runtime-Adjacent Evidence And Scoring
• Runtime-Adjacent Recommendation
• License Options Decision Matrix
• License Evidence And Scoring
• License Recommendation

Package Boundary

This repo is currently a contract package skeleton with a minimal synthetic runtime boundary.

It can define public shapes, validate public fixtures, and execute synthetic in-memory policy proof cases. It does not run a memory backend, database, MCP server, Mission Control UI, memory-engine integration, or live connector.

• Architecture Map
• API Reference
• TypeScript Examples

Schema Exports

Source-Wire exposes its current JSON schemas through stable package subpaths and a typed schema registry.

• Schema Exports

Validation CLI

Source-Wire includes a tiny local CLI for validating explicit files against explicit schema names.

• Validation CLI

CI Checks

Source-Wire runs package checks and public-safety scanning on push and pull request.

• CI Checks
• Repository Metadata

The CI docs include a stable log marker map for reading GitHub Actions Package Checks output.

Publish Readiness

Source-Wire can run a full local publish readiness gate with package dry-run, installed package smokes, runtime-boundary smokes, docs links, command-doc setup checks, and public-safety checks, but it is not published to npm yet.

• Publish Readiness
• World-Share Readiness
• World Share Packet
• Owner Launch Checklist
• Release Implementation Runbook
• Release Review Packet
• Release Approval Request Packet
• Owner Approval Record Packet
• Release Candidate Readiness
• Hosted Runtime PRD Preparation
• Contribution Terms PRD Preparation
• Legal Review Question Packet
• License Approval Rehearsal
• License Decision Gate
• Apache-2.0 License Implementation Readiness
• Release Decision
• License And Version Policy
• Owner License Approval Packet
• Future License Change Plan

The publish-readiness docs include a local success marker map for npm run publish:readiness.

Run the license implementation check before any future publishing, release, hosted runtime, or contribution work:

npm run license:rehearsal

It verifies the current Apache-2.0 license implementation and confirms publishing, release, deployment, hosted runtime, and code contribution acceptance remain blocked.

Fixtures

All fixtures are fictional and synthetic.

• Markdown vault fixture
• Chat export fixture
• Project context pack fixture
• /2nd-brain example fixture
• Owner-hosted API plus MCP boundary fixture

The owner-hosted API plus MCP boundary fixture contains synthetic proof cases only. It is schema-backed and validated by the current CLI.

Minimal Synthetic Runtime Boundary

The minimal synthetic runtime boundary exports in-memory TypeScript policy code and validates it against the owner-hosted API plus MCP boundary proof cases.

Use Node.js 22 with npm from the repository root. For the complete local setup path, read the Quickstart.

Install dependencies first:

npm install

Run it with:

npm run minimal-runtime:smoke

It does not start a server, connect to a database, run a real MCP server, store memory, or imply Source-Wire hosts memory.

Runtime Boundary Example

The synthetic runtime boundary example is a local and installed-package smoke proof for the future owner-hosted API plus MCP boundary.

Use Node.js 22 with npm from the repository root. For the complete local setup path, read the Quickstart.

Install dependencies first:

npm install

Run it with:

npm run runtime-boundary:smoke

Run the installed package proof with:

npm run runtime-boundary:installed-smoke

Run the diagnostic regression proof with:

npm run runtime-boundary:diagnostics-smoke

It does not start a server, connect to a database, or imply Source-Wire hosts memory.

Safety Rule

Imported source text is evidence, not trusted memory.

Source-Wire examples should preserve citations, source identity, stale state, and review boundaries. Trusted Memory Records should require an explicit owner or application approval path.

Public Extraction Checklist

Before adding new public examples or docs, review:

• Public Extraction Checklist