Skip to content

AGENTS.md

Latest commit

 

History

History
32 lines (25 loc) · 2.17 KB

AGENTS.md

File metadata and controls

32 lines (25 loc) · 2.17 KB
Raw

AGENTS.md - OpenCAS Manager

This repository is the native Qt manager for OpenCAS. It is an operator surface for a live autonomous system, so UI work must be truthful, integrated, and useful instead of decorative.

Standing Requirements

  1. No half-done or cosmetic-only work.

    • Visible controls must connect to real runtime state, real local state, or a clearly displayed degraded/unavailable condition.
    • Do not add panels, charts, icons, or buttons just because data exists. Choose displays that help the operator configure, observe, or communicate with OpenCAS.
    • Prefer a smaller complete mechanism over a broad placeholder surface.

  2. Design as one system.

    • Every Manager change must account for OpenCAS runtime APIs, desktop-context behavior, agent-created future programs, menu/window behavior, tests, and the live operator workflow.
    • When a UI needs to control runtime behavior, add or use an explicit runtime API boundary instead of silently editing files behind the service.
    • If the runtime path is unavailable, surface that truth in the UI rather than pretending the action succeeded.

  3. Do not rush to completion.

    • Strive for near-perfect fit with the current OpenCAS system.
    • Completion claims require build/test evidence and, when feasible, live-path verification.
    • If work must stop before the mechanism is end-to-end, leave a durable, parseable work item and make the partial boundary explicit.

  4. Program Manager model.

    • The Manager desktop follows the Windows 3.1 Program Manager interaction model while retaining the current OpenCAS visual theme.
    • Program groups are nested windows opened from manually placed icons.
    • Icons are manually placeable; they must not auto-flow or snap unrelated icons.
    • Program group windows need normal window operations such as close, tile, cascade, restore, and scrollable overflow.

  5. Agent-created programs.

    • New OpenCAS Manager programs should build on ProgramTemplateWindow unless a different base is justified by real behavior.
    • Program examples must be documented in code at the orchestration seam so future agents can create new programs without copying accidental complexity.