Skip to content

[v0.91.8][WP-15][unity][demo] Polish flagship Polis Observatory visual and runtime presentation #5662

Description

@danielbaustin

Summary

Turn the currently functional but visually rough Unity Observatory stage into a
coherent flagship Polis control environment that can be demonstrated live to
investors and inhabitants.

Goal

Deliver an investor-ready Unity Observatory experience with strong spatial
composition, controlled lighting, readable operator surfaces, and truthful live
CSM/Polis runtime presentation.

Required Outcome

The intended FastWork Unity project opens and plays as one polished Observatory
scene whose camera, environment, lighting, UI, runtime state, and operator
interactions work together. The result must consume live runtime truth when it
is available, fail closed when it is not, and retain direct Unity proof at both
1920x1080 and 2560x1440.

Deliverables

  • A composed Observatory environment with a deliberate hero camera, coherent
    circulation, terrain continuity, and no exposed staging voids.
  • A restrained cinematic lighting and post-processing pass that preserves
    material detail and avoids blown cyan highlights, crushed blacks, and
    illegible emissive surfaces.
  • Readable in-world and screen-space Observatory UI with clear iconography,
    hierarchy, connection state, runtime health, agent activity, events,
    governance/evidence state, and operator communication.
  • Real CSM/Polis runtime binding through the repository-owned runtime contract,
    with explicit connected, degraded, disconnected, and demo-data states.
  • Focused interaction for inspecting agents, runtime state, event activity, and
    operator communication without blocking the scene view.
  • Retained editor/MCP identity proof, Play Mode proof, and visual evidence at
    1920x1080 and 2560x1440 from the intended project and scene.

Acceptance Criteria

  • The hero view has a clear focal Observatory structure, readable foreground,
    middle ground, and background, and a composed route into the environment.
  • Camera framing does not clip major architecture or expose accidental voids,
    floating terrain edges, disconnected ramps, or unfinished staging geometry.
  • Lighting preserves readable materials and depth; emissive cyan is an accent,
    not the dominant exposure, and dark regions retain intentional detail.
  • UI text and icons remain crisp, aligned, non-overlapping, and legible at
    1920x1080 and 2560x1440 without page-level scrolling.
  • The runtime surface identifies whether data is live, degraded, disconnected,
    or demonstrative and never presents fixture data as live Polis truth.
  • Live mode consumes repository-owned CSM/runtime contracts for agent, event,
    health, governance/evidence, and communication state where those contracts
    exist; unsupported fields remain explicit non-claims.
  • Operator controls can select an agent or subsystem, inspect current state,
    observe event flow, and send a bounded communication through the supported
    runtime contract or fail closed with an exact reason.
  • One direct Unity proof shows the intended project, loaded flagship scene, Play
    Mode result, and retained 1920x1080 and 2560x1440 captures.
  • Focused validation passes without building player binaries or replacement
    owner binaries.
  • Every Unity-MCP, editor, runtime, asset, or proof-tool anomaly discovered
    during execution is retained in this issue or routed to a named follow-up.

Repo Inputs

Dependencies

Demo Expectations

  • The first Play Mode view should already read as the Observatory, not as an
    editor staging pile.
  • The scene should make the Polis visible as a living governed system through
    spatial activity, agent/runtime state, event flow, evidence, and operator
    communication.
  • Visual quality should support a live investor walkthrough, while every
    runtime and readiness claim remains directly evidenced.

Non-goals

  • Do not build standalone player binaries.
  • Do not build replacement ADL, C-SDLC, Unity-MCP, or other owner binaries.
  • Do not republish licensed asset packs or silently move multi-gigabyte asset
    payloads into Git.
  • Do not absorb WP-14A platform acceptance, unrelated release-tail work, or
    v0.92 birthday claims.
  • Do not claim production cloud integration, complete investor readiness, or
    runtime semantics that are not shown in direct proof.

Issue-Graph Notes

Tooling Notes

  • Use typed C-SDLC v2 lifecycle routing for every lifecycle step.
  • Work only in the issue-bound FastWork worktree and the intended Unity project.
  • Create an issue-bound goal before implementation starts.
  • Use Unity-MCP/editor tools for scene edits and direct proof.
  • Use repository-installed binaries only and permission-safe process checks.
  • Do not use raw gh, broad process scans, cloud fallback, or secret-bearing
    output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:demotrack:roadmapRoadmap-level worktype:taskImplementation task under a featureversion:v0.91.8ADL v0.91.8 milestone scopewp:WP-15v0.91.5 work package 15 ordering label

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions