Files
prometeu-studio/docs/specs/README.md
T
bquarkz 71fb80efc3
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit
feat(studio): ship JavaFX 2 Play and delegate integration tooling
Launch the JavaFX 2 project shell on Java 25 with an interactive viewport,
managed Play lifecycle and project mutation guards. Preserve headless/MCP and
save compatibility, and qualify exact runtime executable bundles.
Separate unit JaCoCo gates from opt-in integration suites and use the internal
Pong fixture for the headless visual pilot.
Move maintenance and native conformance tools into tooling; retain the VS Code
extension and update current navigation links.

Validation: tooling make verify passed, including 1064 Studio unit tests,
JaCoCo thresholds and 22 headless integration tests.
2026-11-19 17:32:03 +00:00

39 lines
2.1 KiB
Markdown

# Specification Guide
Specifications live under this tree and are organized by contract owner:
| Owner | Canonical corpus | Responsibility |
| --- | --- | --- |
| `compiler/general` | [General compiler](compiler/README.md) | Shared compilation, linking, typed handoff, emission and acceptance |
| `compiler/pbs` | [PBS language](compiler-languages/pbs/README.md) | PBS source, semantics, SDK and frontend projections |
| `packer` | [Packer](packer/README.md) | Assets, artifacts, packing and diagnostics |
| `studio` | [Studio](studio/README.md) | Shell, workspaces, adapters and visual/automation integration |
New compiler languages receive their own corpus under `compiler-languages/`.
Shared compiler policy stays in `compiler/`; PBS is not the root for other domains.
Each domain README provides a chapter index and reading order. Numbered chapters
are normative within their stated scope. Feature chapters own their detailed
contracts; cross-cutting chapters reference those rules rather than maintaining
competing versions. Write specifications and durable lessons in English.
The runtime repository owns PBX, ISA, admission and VM execution. Studio's
[VM architecture references and catalog mirrors](../vm-arch/README.md) retain
their separate provenance and synchronization policy. [Roadmaps](../roadmaps/)
describe cross-domain planning, not an alternative contract source.
Engineering discussions, decisions, plans and execution evidence are maintained
in the enclosing workspace's [AI Engineering project](../../../.ai-engineering/README.md).
Published lessons and supporting assets remain in `discussion/lessons/`.
See [repository instructions](../../AGENTS.md).
## Navigation verification
Run `../tooling/.venv/bin/python ../tooling/scripts/documentation/verify.py --root .`
from the Studio repository root to check local
links and anchors. Pass `--runtime ../runtime` to also check provider references
against an available read-only runtime checkout. The byte-exact architecture/ISA
mirrors retain the link context of their runtime originals; the checker resolves
them there. Ordinary builds and installed documentation reads do not require that
checkout.