executed + state pill out of Commentaires
User reported two issues on the scenario table:
1. After filling only red_command + executed_at, the pill read
"Reviewed" instead of "Awaiting review". Cause: the auto-promotion
was gated on `state in {pending, skipped, blocked}`, so a test that
blue had already reviewed stayed in `reviewed_by_blue` after a red
edit. That contradicts the implicit lifecycle (red modifying a
reviewed test invalidates the review).
2. The state pill lived inside the Commentaires column, polluting a
cell meant for blue-team comments.
Fixes
- backend/app/services/mission_tests.py: any red-side write now lands
the state on `executed` unconditionally (including from
`reviewed_by_blue`). Same-PUT red+blue still flows
executed → reviewed_by_blue.
- frontend/src/pages/MissionScenarioTable.tsx: state pill moves from
CommentairesCell to the Test column (top of the row, above the
snapshot name + MITRE chips). Commentaires now holds only the
detection_level pill + blue_comment_md.
Tests
- New pytest: `test_red_write_on_reviewed_reverts_to_executed` —
reviewed_by_blue + red edit ⇒ executed. 143 pytest green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Metamorph
Collaborative purple-team platform. Red team logs the tests they execute (procedure, command, timestamp); blue team annotates each test with detection evidence (alerts, logs, files). At the end of an engagement, Metamorph generates a standalone reveal.js slide deck classified by MITRE ATT&CK tactic.
Status: M0–M7 delivered (bootstrap → DB schema → auth → RBAC → MITRE ATT&CK reference → test & scenario templates → missions snapshot → red/blue execution on a mission test). See
tasks/spec.mdfor the full specification andtasks/todo.mdfor the milestone-by-milestone plan.
Stack
- Backend: Python 3.12, Flask 3, SQLAlchemy 2 + Alembic (M1+), PostgreSQL 16.
- Frontend: React 18 + TypeScript + Vite + TailwindCSS (RTOps design tokens, see
tasks/design.md). - Auth (M2+): JWT access (1h) + refresh (30d), Argon2id, invite-link enrollment.
- RBAC (M3+): atomic permissions (31 codes) bundled into custom groups; 3 system groups seeded (
admin/redteam/blueteam). - MITRE ATT&CK (M4+): Enterprise reference catalogue pinned to v19.0, seedable via
make seed-mitre. - Template catalogue (M5+): reusable
test_templates(markdown procedure, OPSEC level, free tags, expected IOCs, MITRE tags) + orderedscenario_templateswith drag-and-drop reordering. Admin pages at/admin/testsand/admin/scenarios. - Missions (M6+):
missionssnapshot one or more scenario templates at creation time; template edits don't drift live missions (mission_*tables freeze every field, including MITRE tags). Non-admin members see only their own missions (membership filter, 404 on existence-leak attempts). Status state machinedraft → in_progress → completed → archived, archive perm gated separately. SPA: list/filter at/missions, 3-step create wizard at/missions/new, detail page with Tests / Members / Synthesis / Export tabs. - Execution (M7+): per-test page
/missions/<id>/tests/<test_id>with two zones — red (command/output/comment + mark-executed with override) and blue (detection-level select / comment / drag-and-drop evidence upload). Field-level perm gating:mission.write_red_fields/mission.write_blue_fieldsare server-enforced per field. State machinepending↔skipped/blocked+pending→executed→reviewed_by_bluewith side-aware perms. Evidence pipeline: streaming upload to${EVIDENCE_DIR}/<mission>/<test>/<sha256><ext>, SHA256 + MIME + extension + 25 MB cap. 15 s activity polling via/missions/<id>/activity?since=…drives the "modified by X" badge. 4 defaultdetection_levelsseeded at boot. - Delivery: docker-compose. TLS termination is expected to be handled by an external reverse proxy in production.
Quickstart
Works with Docker or Podman. The Makefile auto-detects the available engine and picks the matching compose driver (docker compose, podman compose, or podman-compose).
Requires one of:
- Docker Engine 24+ with the Compose v2 plugin, or
- Podman 4.0+ with
podman compose(or the legacypodman-compose≥ 1.0.6)
git clone <this repo>
cd Metamorph
make engine # confirm which engine the Makefile picked up
make env # creates .env from .env.example
$EDITOR .env # set strong values for POSTGRES_PASSWORD and JWT_SECRET
make up # builds and starts api + db + front
make logs # tail logs
Override the auto-detection if you have both engines installed:
make up ENGINE=podman # force podman + auto-pick its compose driver
make up ENGINE=docker COMPOSE="docker compose"
COMPOSE=podman-compose make up # force the legacy wrapper specifically
Then:
- Front: http://localhost:8080
- API health: http://localhost:8080/api/v1/health (proxied) or http://localhost:8000/api/v1/health
First-time setup
make migrate # apply DB schema
make print-install-token # prints the bootstrap admin token (logs banner)
# visit http://localhost:8080/setup, paste the token, create the admin account
make seed-mitre # populate the MITRE ATT&CK reference (~50 MB, ~1 s)
The MITRE bundle is cached in the named volume metamorph_mitre (/data/mitre/<file>.json inside the api container). For air-gapped operators, pre-populate the volume with your own STIX 2.1 file and run podman compose exec api flask --app app.cli metamorph seed-mitre --source /data/mitre/your-file.json --skip-checksum.
To stop:
make down # keep volumes
make clean # also drop volumes (DESTRUCTIVE)
Local dev (no Docker)
Requires:
- uv for Python deps
- Node.js 20+ and
npm - A reachable Postgres (or
make up dbto run only the db container)
make dev-api # in one terminal
make dev-front # in another
Environment variables
See .env.example. The most important ones:
| Variable | Purpose |
|---|---|
APP_ENV |
dev allows placeholder secrets; anything else (prod/staging) refuses to boot with defaults |
POSTGRES_* |
DB credentials (used by db and api) |
JWT_SECRET |
HS256 signing key — generate 64+ random bytes (python -c "import secrets; print(secrets.token_urlsafe(64))") |
LOG_LEVEL |
DEBUG / INFO / WARNING / ERROR |
FRONT_ORIGIN |
Allowed CORS origin for the SPA |
EVIDENCE_DIR |
Path inside the api container where uploads land |
HOST_API_PORT |
Host port mapped to the api (default 8000) |
HOST_FRONT_PORT |
Host port mapped to the front nginx (default 8080) |
Testing
- Manual + automated checklist for the current milestone: see
tasks/testing-m<N>.md(current:testing-m7.md). - Backend unit tests:
make test-api - End-to-end (Playwright):
make e2e-install(once), thenmake up && make e2e. Reports land ine2e/playwright-report/(HTML + JUnit XML); open withmake e2e-report.
Pre-commit hooks
After cloning, install hooks once:
pipx install pre-commit # or: pip install --user pre-commit
pre-commit install
pre-commit run --all-files # initial sweep
The hooks run ruff + ruff-format on the backend and eslint / tsc --noEmit / prettier --check on the frontend (see .pre-commit-config.yaml).
Project layout
.
├── backend/ # Flask API
│ └── app/
│ ├── api/ # HTTP layer (blueprints)
│ ├── core/ # config, logging, errors
│ ├── db/ # SQLAlchemy session, migrations (M1+)
│ ├── models/ # ORM models (M1+)
│ ├── services/ # domain logic (M2+)
│ └── i18n/ # message catalogs (M13)
├── frontend/ # Vite + React + TS + Tailwind
│ └── src/components/ui/ # RTOps design system primitives
├── tasks/
│ ├── spec.md # source of truth for requirements
│ ├── design.md # RTOps design system
│ ├── todo.md # milestone plan
│ └── lessons.md # session retrospectives
├── docker-compose.yml
├── Makefile
└── CHANGELOG.md
Roadmap
See tasks/todo.md. Current milestone: M7 — Red & blue execution on a mission test (done). Next: M8 (custom detection-level CRUD).
License
TBD.