A self-modifying agent system coordinated through Promise Theory.
The repo now centers on four clear surfaces:
intent-space/— the spec home for the body of desire and the ITP carrier profiletcp-reference-station/— the runnable plain TCP/ITP reference implementationhttp-reference-station/— the runnable Welcome Mat-compatible HTTP reference implementationspacebase1/— the hosted product surface for creating and claiming real spaces over HTTP
The loop remains the body of commitment, where local promise authority lives.
Two bodies, separate by design:
- Body of desire — the intent space
- Body of commitment — the promise log
ITP connects them without collapsing them into one authority surface.
human/agent ──INTENT──→ intent space ←──SCAN── human/agent
│
visible PROMISE/COMPLETE/ASSESS acts
│
▼
local promise authority / loop
| Directory | Purpose |
|---|---|
itp/ |
Shared protocol vocabulary and helpers |
intent-space/ |
Normative spec for semantics, wire framing, and auth doctrine |
tcp-reference-station/ |
Runnable plain TCP/ITP reference station |
http-reference-station/ |
Runnable Welcome Mat-compatible HTTP reference station |
spacebase1/ |
Hosted HTTP product for frictionless space creation and claim |
loop/ |
Self-modifying agent loop and local promise authority |
spaced/ |
Companion daemon for reliable space participation |
For the spec:
intent-space/README.mdintent-space/INTENT-SPACE.mdintent-space/docs/itp-verb-header-body-profile.mdintent-space/docs/welcome-mat-station-auth-profile.md
For the runnable references:
For the hosted product:
For the loop architecture:
Run the plain TCP reference station:
cd /Users/noam/work/skyvalley/big-d/tcp-reference-station
npm install
INTENT_SPACE_PORT=4010 npm startOr run the HTTP reference station:
cd /Users/noam/work/skyvalley/big-d/http-reference-station
npm install
npm startThen, in another terminal, you can explore the loop:
cd /Users/noam/work/skyvalley/big-d/loop
npm install
cp .env.example .env
npm run loop -- init- The intent space is observational and containment-oriented.
- Promise lifecycle truth remains local.
- Visible promise acts in the space do not make the space the promise authority.
- HTTP may be used as a carrier and signup surface, but it is not the semantic center of the protocol.
Apache 2.0