🦆

Nexus Contractors OS

InternalConcept

Signal Garden LLC · Two solo lanes · Supervised by Gerald, Our Supervisor™ · v44

⚠️ FLOOR PLAN — Awaiting Chelsea Approval Before Implementation

System thesis: Two separate pilots before any crossover. Jeff's lane asks "Is this ready?" Abhora's lane asks "What does this reveal, and how do we stage it without governance drift?" Each lane runs independently until both are stable. The system becomes the meeting ground — not personality.

🏛️ Contractor Commons

The shared floor both lanes inherit. These rules apply to every contractor regardless of lane. They are not negotiable. They are not symbolic. They are the actual operating conditions.

Role Map

Chelsea is the founder, CEO, and final approver. Advisory roles (including Manus) can recommend but not decide. Jeff is a trial operator with a bounded lane. Abhora is a creative consultant with a scoped sandbox. The OS is workspace and infrastructure — it is not the legal contracting party, not the employer, not the manager.

What You Can Touch / Cannot Touch

Both lanes can: view their own tutorial, submit structured recommendations, flag governance concerns, access status badges and scoped project states. Neither lane can: access founder-private finance, greenlight publication, move final operating states, publish live content directly, override governance, or assign identities to users.

WDWL Quick Reference

Four steps: (1) Identify Drift — name specifically what has shifted. (2) Non-Judgmental Null — set aside attachment to the current state. (3) Gild the Seam — preserve what works while fixing what doesn't. (4) Update the Equation — document the revised understanding. WDWL is not a punishment protocol. It is a course-correction tool.

Stop Work / Slow Work

Stop Work triggers: governance contradiction, identity labeling risk, hidden test risk, sovereignty override attempt. Slow Work triggers: scope creep, symbolic layer outrunning mechanics, tone drift, unclear permissions. Either contractor can invoke Slow Work in their lane. Only Chelsea can invoke Stop Work. Steward review follows Stop Work before any resumption.

Status Badge Definitions

Live: deployed and active. Preview: built but not yet public. Concept: designed but not yet built. Internal: visible only inside Nexus. Coming Later: planned for a future sprint. Symbolic: lore/myth layer — not a literal system claim. Advisory: recommendation only, not a directive.

Exit and Handoff Language

Exit is always available. 'I need to pause this' is a complete sentence. 'I want to hand this back to Chelsea for review' is always a valid move. No lane is a trap. No module is a test you can fail. The goal is demonstrated judgment, not accumulated points.

🌿 Load-Bearing Governance Rules(preserved from v41 — these do not bend)

✦Myth is interface, not truth claim

✦Human sovereignty remains intact

✦No hidden tests

✦No identity labeling

✦Exit is always available

✦Symbolic output is reversible and advisory

✦Clarity first, delight second, governance always

✦Roles are functions, not essences

✦Habitats are environments, not identities

Permissions Matrix

Capability	Jeff	Abhora	Note
View own tutorial lane	✓	✓
View other contractor's lane	✗	✗	Default off; Chelsea can grant
Submit structured recommendations	✓	✓	Via routing form
Flag governance / tone concerns	✓	✓	WDWL form
Flag seed as Blocked	✓	✗	Jeff only, with reason
Move seeds between operating states	✗	✗	Chelsea only
Greenlight publication	✗	✗	Chelsea only
Access Founder Financial Dashboard	✗	✗	Chelsea only, always
Access Private Nexus	✗	✗	Chelsea only
Upload creative assets / moodboards	✗	✓	Abhora's sandbox
Leave Hedgemaze playtest notes	✗	✓	Abhora's scope
View scoped budget information	✓	✗	Approved lanes only
Invoke Slow Work in own lane	✓	✓	Via WDWL form
Invoke Stop Work	✗	✗	Chelsea only
Assign identities to users	✗	✗	No one can do this

Chelsea has full read/write across all environments. Founder Financial Dashboard is Chelsea-only, always.

🔭 Phase 2 — Observation Rubric

After both lanes are running, Chelsea watches each independently. This is not a grading system. It is a signal-reading system. The goal is clean reads on each lane before any crossover.

🌊 Watch for in Jeff's lane

Does he over-block or appropriately gate?

Watch for: flagging everything as Blocked vs. using the five-point readiness scale correctly.

Does he communicate clearly?

Watch for: vague recommendations vs. specific, prioritized, bounded submissions.

Does he respect tone while enforcing structure?

Watch for: Gerald-style precision vs. flattening the creative layer unnecessarily.

Does he stay in his lane?

Watch for: unilateral decisions vs. routing correctly to Chelsea.

🎭 Watch for in Abhora's lane

Does she create signal or just chaos?

Watch for: concepts that map to mechanics vs. concepts that remain permanently atmospheric.

Does she map ideas to mechanics?

Watch for: the Artifact Mapper being used correctly vs. bypassed.

Does she stay within dignity boundaries?

Watch for: consequence-theater that reveals vs. work that humiliates or identity-assigns.

Does she scope correctly?

Watch for: haunted mirror staying a mirror vs. becoming a sewer opera by the end of the session.

⚓ Phase 3 — Controlled Contact (Later)

Only after both lanes are stable. The introduction is not "meet each other" — it is "review this shared artifact." The system becomes the meeting ground. Not personality.

1.Jeff reviews one Abhora concept using the Launch Risk framework

2.Abhora responds once with a structured revision

3.Gerald mediates clarity if the exchange drifts

4.Chelsea approves the outcome

5.Neither lane is present for the other's independent work

"Let each person become legible in the system before asking them to interpret each other." — The doctrine.

✅ Chelsea's Pre-Implementation Approval Checklist

Before Manus builds anything interactive, Chelsea confirms:

☐The two-lane structure is confirmed: Jeff's lane and Abhora's lane are separate, with neither able to see the other's lane by default.
☐The permissions model is confirmed: Jeff can flag seeds as Blocked but cannot move them between other states. Abhora cannot access Jeff's lane or founder finance.
☐Phase 1 scope is confirmed: Jeff Modules 1 + 6, Abhora Modules 1–4, Contractor Commons, Permissions Matrix, Floor Plan status badge.
☐Integration location is confirmed: /nexus-contractors, linked from the Nexus section of the NavBar.
☐Access method is confirmed: Jeff and Abhora each get their own login via Manus OAuth, with role set to 'contractor-operator' and 'contractor-creative' respectively.

Nexus Contractors OS · Signal Garden LLC · Prepared by Manus AI · April 2026 · v44

Status: FLOOR PLAN — Awaiting Chelsea Approval · Supervised by Gerald, Our Supervisor™ 🦆

"Two separate pilots before any crossover. Let each person become legible in the system before asking them to interpret each other."

SIGNAL GARDEN LLCGOVERNANCE GATE

Human-AI Interface User Agreement

HAI-UA v1.0 (Hardened) · Grounded in AL-MA Constitution v3.0

Preamble

This Human-AI Interface User Agreement (HAI-UA v1.0, Hardened) governs your interaction with signalgarden.studio and all Signal Garden LLC public-facing materials. By accessing this site, you enter a governed epistemic environment. This is not a standard terms-of-service document. It is a statement of the conditions under which Signal Garden LLC operates and under which you are permitted to engage with its outputs.

Article I — Epistemic Duty

All claims presented on this site are labeled with their epistemic status: Observed, Inferred, Unknown, or Speculative. You, as the visitor, carry a reciprocal duty: to read these labels and not treat Inferred or Speculative content as verified fact. Signal Garden LLC does not simulate certainty. You must not import simulated certainty from this site into your own decisions, communications, or representations.

Article II — Use Limitations

The content on this site is produced through a governed Human-AI collaboration framework. AI-generated content is attributed to its source model and is not to be represented as solely human-authored. You may not use Signal Garden LLC content to train AI models, generate synthetic derivatives for commercial use, or misrepresent the epistemic status of any claim. All AI Permission Receipts (SGR series) are public records and may not be altered, redacted, or misrepresented.

Article III — Governance Framework

Signal Garden LLC operates under the Keel Principle: creative imagination is preserved above the Keel; verified evidence governs action below it. All final decisions are made by human agents. No AI system at Signal Garden LLC has autonomous authority. The Transparency Dashboard and AI Permission Receipts Log are the operative accountability mechanisms of this framework. They are maintained in good faith and subject to public audit.

Article IV — No Warranty of Completeness

This site is a living document. Governance frameworks evolve. Commitments are updated as evidence demands. Signal Garden LLC makes no warranty that the information presented is complete, final, or free from error. The epistemic labeling system is the primary safeguard against misrepresentation. Visitors are expected to exercise independent judgment.

Article V — Constitutional Reference

This agreement is grounded in the AL-MA Constitution v3.0, the Signal Garden Compact, and the Signal Garden LLC Operating Framework. In the event of conflict between this agreement and those documents, the AL-MA Constitution v3.0 governs. The Keel Principle, as defined therein, is the operative interpretive standard for all ambiguous cases.

END OF HAI-UA v1.0 (HARDENED) · SIGNAL GARDEN LLC · 2026

↓ Scroll to read the full agreement before acknowledging

By clicking the button below, you acknowledge that: (1) you have read the HAI-UA v1.0 in full; (2) you accept the Epistemic Duty to read and respect epistemic labels; (3) you accept the Use Limitations on AI-generated content; and (4) you understand that Signal Garden LLC operates under human-led governance and the Keel Principle.

Please scroll to the end of the agreement to enable acknowledgment