stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
505fe7a885cafe21d0a500d33436f99503b435c0
git.stella-ops.org/src/Web/StellaOps.Web/AGENTS.md
StellaOps Bot ef6e4b2067
Some checks failed
AOC Guard CI / aoc-guard (push) Has been cancelled
Details
AOC Guard CI / aoc-verify (push) Has been cancelled
Details
Docs CI / lint-and-preview (push) Has been cancelled
Details
Policy Lint & Smoke / policy-lint (push) Has been cancelled
Details
api-governance / spectral-lint (push) Has been cancelled
Details
oas-ci / oas-validate (push) Has been cancelled
Details
Policy Simulation / policy-simulate (push) Has been cancelled
Details
sdk-generator-smoke / sdk-smoke (push) Has been cancelled
Details
SDK Publish & Sign / sdk-publish (push) Has been cancelled
Details
Merge branch 'main' of https://git.stella-ops.org/stella-ops.org/git.stella-ops.org
2025-11-27 21:45:32 +02:00

2.1 KiB
Raw Blame History

StellaOps Web Frontend

Mission

Design and build the StellaOps web user experience that surfaces backend capabilities (Authority, Concelier, Exporters) through an offline-friendly Angular application.

Team Composition

  • UX Specialist – defines user journeys, interaction patterns, accessibility guidelines, and visual design language.
  • Angular Engineers – implement the SPA, integrate with backend APIs, and ensure deterministic builds suitable for air-gapped deployments.

Operating Principles

  • Favor modular Angular architecture (feature modules, shared UI kit) with strong typing via latest TypeScript/Angular releases.
  • Align UI flows with backend contracts; coordinate with Authority and Concelier teams for API changes.
  • Keep assets and build outputs deterministic and cacheable for Offline Kit packaging.
  • Track work using the local TASKS.md board; keep statuses (TODO/DOING/REVIEW/BLOCKED/DONE) up to date.

Key Paths

  • src/Web/StellaOps.Web — Angular workspace (to be scaffolded).
  • docs/ — UX specs and mockups (to be added).
  • ops/ — Web deployment manifests for air-gapped environments (future).

Coordination

  • Sync with DevEx for project scaffolding and build pipelines.
  • Partner with Docs Guild to translate UX decisions into operator guides.
  • Collaborate with Security Guild to validate authentication flows and session handling.

Required Reading

  • docs/modules/platform/architecture-overview.md

Working Agreement

    1. Update task status to DOING/DONE in both correspoding sprint file /docs/implplan/SPRINT_*.md and the local TASKS.md when you start or finish work.
    1. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
    1. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
    1. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
    1. Revert to TODO if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.