Real IntelligenceOS 1.1.1 output for the fictional Relay Desk project. Local paths are redacted and navigation adapted for this public sample. Supporting kit files mentioned below are not part of this preview.

IntelligenceOS Project Map

Relay Desk

Open this first. It turns the report folder into a plain-English map of what IntelligenceOS found and what the next agent needs to know before editing.

What IntelligenceOS found

IntelligenceOS scanned a local source folder in read-only mode and created a project map, report, handoff files and local evidence artefacts.

Project type
codebase
Source type
Code repository
Source folder
~/Projects/relay-desk
Live writes
false
Secrets handled
false
Evidence captured
19 Sep 2026 · local folder

Project purpose

Outcome: keep client requests, decisions and proof in one readable local record

Intended users: independent studios handling a small number of active client projects

Definition of done

Protected paths or actions

Review before sharing

Local source files may contain private information. Do not share raw reports or databases unless reviewed.

Privacy

Project snapshot

7items found
2code files
3docs/content files
2config files
0web files
3surfaces
1quality flags

Important files

  • README.mdCommon project entry point or configuration file.
  • site-intel.ymlCommon project entry point or configuration file.
  • pyproject.tomlCommon project entry point or configuration file.
  • docs/architecture.mdIncluded in the local project scan.
  • docs/release-checklist.mdIncluded in the local project scan.
  • src/relay_desk.pyIncluded in the local project scan.
  • tests/test_tasks.pyIncluded in the local project scan.

Detected surfaces

  • Application repositoryrepository | source_control | .
  • Unit teststest_suite | proof_plane | tests
  • Product notesdocument_store | human_read_model | docs

How This Repository Works

Detected local contracts for the next agent to verify before changing code.

Configured Gates And Evidence

No project gates were declared in site-intel.yml.

Warnings and gaps

What the next agent needs to know

  • The project outcome is: keep client requests, decisions and proof in one readable local record
  • Start with site-intel.yml at ~/Projects/projects/relay-desk/site-intel.yml.
  • Treat PROJECT_MAP.html as the buyer-facing summary and agent-handoff.md as supporting context.
  • The scan found 7 inventory items and 1 quality flags.
  • Do not publish, deploy, write to a CMS, use credentials, call paid APIs or run destructive commands without explicit approval.
  • If project changes affect files, docs, topology, metadata, links, workflows or quality gates, rerun IntelligenceOS before closeout.
  • Definition of done: a request can be recorded with an owner and next action; completed work keeps a short evidence note; the local test suite passes before release
  • Protected paths or actions: client-data/, .env
  • Detected verification commands: python3 -m unittest discover (test layout; discovered, not owner-approved).

What To Do Next

  • Read the Project Map.
  • Open the browser report if you want detail.
  • Give NEXT_AGENT_PROMPT.md and agent-handoff.md to your agent for a plain-English explanation.
  • Approve only a scoped next action with files, proof and rollback named.

Optional follow-on work