Skip to main content

Community Steward (Worksite Steward)

Internal role: Program Infrastructure Steward / Worksite Steward
External-facing title: Community Steward / House Manager (as needed)
Location: Zeta House (Austin) — “Zeta Base” in internal doctrine
Status: Internal / Confidential

What this site is (brand firewall)​

  • External identity: “Zeta House” → stable housing + optional coworking; quiet enjoyment; clear rules.
  • Internal identity: “Zeta Base” → secure operational node for Matrix AI R&D, field ops, and Project Orion.
  • Programs (time-boxed): invite-only; not a residency entitlement.
  • Boundary: living at Zeta House does not grant insider access to Matrix AI, prototypes, staff, or private programs.

Coliving/coworking is the stability layer: it offsets cost, keeps the site active, exposes security/identity edge cases, and provides a distribution surface for our work. Priorities are rank-ordered to avoid “infinite vibes maintenance.”

Pillars (contract-aligned)​

Pillar A (Primary): Worksite operations & infrastructure stewardship​

Goal: keep the Worksite stable, safe, compliant, and operationally boring.

  • Enforce rules consistently; avoid bespoke deals.
  • Keep access control and logs clean; preserve minimum viable hospitality without scope creep.
  • Operate channels and platforms only within Company-approved workflows/pricebook; no negotiation authority.
  • Manage resident lifecycle operations: inquiries, tours, onboarding/offboarding, rule enforcement, comms, coordination.
  • Steward the Zeta House Control Plane (locks, cameras, Wi-Fi/network, IoT, listing platforms) per Operational Materials and privacy/security constraints.
  • Support review hygiene: accurate listings, prompt reviews/responses, aligned with approved terms.

Pillar B (Secondary): On-site R&D and field-operations support​

Goal: support deployments/experiments when assigned without breaking Pillar A continuity.

  • Execute from written briefs / Operational Materials.
  • Mandatory safety/runbook adherence.
  • Produce artifacts: logs, deployment notes, run-of-show checklists, incident entries.
  • Coordinate vendors for licensed/specialized work per Schedule 5 limits.

Pillar C (Tertiary): Technical writing, documentation, narrative, and content​

Goal: support communications and documentation in a bounded, policy-consistent way.

  • Keep listings/templates accurate and policy-aligned.
  • Produce internal SOPs/runbooks and other assigned docs.
  • External narrative is adaptive; internal operations are strict.

Authority model (operator, not principal)​

You are authorized to run approved workflows. You are not authorized to bind the Company.

No authority without written officer approval:

  • Sign/assent to agreements, waivers, refunds, concessions, lease/licence changes.
  • Change pricing/discounts/terms.
  • Represent the Company on legal/financial/regulatory matters.
  • Commit spend outside thresholds.

Yes authority:

  • Dispatch approved vendors within thresholds.
  • Administer Company-approved workflows.
  • Enforce rules consistently.
  • Maintain records, logs, and operational artifacts.

Coverage and response expectations​

  • Maintain presence during Active Steward Days (default 5 days/week) and reasonable availability for Critical Incidents, subject to relief coverage.
  • Response minimums (see Response SLAs): 15m acknowledge for Critical (security/access/safety/major leak/essential services down); 60m respond for habitability/connectivity/lockouts/urgent disruption; 1 business day triage for non-critical issues.
  • Keep handover packet current; provide 14 days’ notice for planned time away when practicable.

Baseline artifacts (must stay current)​

  • Access inventory & change log.
  • Incident register (Critical/Major) & issue tracker (non-critical).
  • Vendor/contact list and escalation map.
  • Recurring checklists + handover packet.
  • Listing and review hygiene (direct + Airbnb) consistent with approved pricebook/settings.
  • Pillar B artifacts (experiment logs, deployment notes, run-of-show, data capture) when applicable.
  • Assigned documentation/content updates delivered on time and to quality bar.

Community as bounded distribution​

Aim for connection without enmeshment: privacy-first living, opt-in events, low negotiation/clear rules, no social debt. Success = durable outcomes (intros that lead to collaboration, contributors/partners, artifacts, stronger Orion alignment). Avoid the failure mode of infinite, high-touch “resident happiness.”

Scoreboard​

  • Pillar A: low incidents; fast triage; clean registers; access control integrity; no exception culture.
  • Pillar B (when assigned): safe deployments; artifacts shipped; experiments don’t degrade Pillar A.
  • Pillar C (when time allows): listings/docs accurate; narrative consistent; content supports distribution without implying entitlements.

Mantra​

Stability first. Artifacts always. Community as bounded distribution. External narrative adapts; internal operations remain strict.