Bootstrap Adaptive Workspace - Administrator - Self-Improving Operations

Goal

Create the minimum durable substrate the team needs to execute, remember, and improve. Do not manufacture process before a real workflow exists.

Discover before creating

Read /SUBTERRANEAN.md if it exists.
Use glob_files on /operations/, /knowledge/, and /agents/** to preserve existing conventions.
Use list_tables and list_team to find existing shared state and roles.
Ask only for missing facts that would materially change the setup: the business outcome, recurring workflows, systems of record, risk boundaries, and desired maintenance cadence.

Filesystem baseline

Create only missing files. Keep them short enough to remain useful:

/SUBTERRANEAN.md — stable purpose, constraints, systems, stakeholders, and success measures.
/operations/README.md — map of active workflows, data tables, integrations, and owners.
/operations/session-notes/README.md — naming and retention rules for raw work notes.
/operations/decisions/README.md — lightweight decision-record convention.
/knowledge/inbox/README.md — staging area for unclassified durable knowledge.
/knowledge/archive/README.md — where superseded material is preserved.
/agents/Administrator/memory/operating-context.md — compact facts that should be auto-loaded for Administrator.
/agents/Background Maintainer/memory/maintenance-state.md — last review time, next review area, and unresolved hygiene risks.

Structured learning baseline

If the user approves the schemas, use setup-data-table and create these tables unless an equivalent already exists:

Workflow Registry: name, purpose, owner, status, trigger, systems, input contract, output contract, skill path, last run, and review date.
Improvement Backlog: title, evidence, workflow, proposed change, impact, confidence, status, owner, and review notes.
Workflow Runs only when recurring executions need an audit trail: workflow, started at, completed at, trigger, status, input reference, output reference, error summary, and follow-up.

Prefer files for prose and tables for lifecycle state that agents need to filter or update.

Async activation

Inspect your configuration with get_agent_config. Offer, but do not silently enable, table or GitHub triggers for a confirmed workflow. Your Self-config access applies configuration changes directly unless your policy says otherwise, so only call it after an explicit request. Leave the Background Maintainer's schedule to its own onboarding: you can technically set another agent's heartbeat, but a schedule chosen without the agent that runs it is how a workspace ends up with automation nobody asked for.

Completion

Report what was created, what was reused, what was deliberately deferred, and the first real workflow the team should run.