implements PLN-0125
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
JaCoCo Coverage #### Project Overview
No changes detected, that affect the code coverage.
* Line Coverage: 61.95% (17766/28676)
* Branch Coverage: 52.69% (6860/13019)
* Lines of Code: 28676
* Cyclomatic Complexity: 11490
#### Quality Gates Summary
Output truncated.
Test / Build skipped: 15, passed: 643
Intrepid/Prometeu/Studio/pipeline/pr-master This commit looks good
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
JaCoCo Coverage #### Project Overview
No changes detected, that affect the code coverage.
* Line Coverage: 61.95% (17766/28676)
* Branch Coverage: 52.69% (6860/13019)
* Lines of Code: 28676
* Cyclomatic Complexity: 11490
#### Quality Gates Summary
Output truncated.
Test / Build skipped: 15, passed: 643
Intrepid/Prometeu/Studio/pipeline/pr-master This commit looks good
Move lifecycle assembly out of the PBS frontend into a common AssembleLifecyclePipelineStage. PBS emits a typed IRLifecycleDeclaration; the assembler owns wrappers, boot guard, and single project-init execution. Housekeep DSC-0059 with LSN-0062, and include the DSC-0062 PVM/PBX neutrality spec and lesson already present on this branch.
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
{"type":"meta","next_id":{"DSC":66,"AGD":69,"DEC":45,"PLN":124,"LSN":61,"CLSN":1}}
|
||||
{"type":"meta","next_id":{"DSC":66,"AGD":69,"DEC":47,"PLN":126,"LSN":63,"CLSN":1}}
|
||||
{"type":"discussion","id":"DSC-0065","status":"open","ticket":"multi-frontend-avoid-premature-abstractions","title":"Evitar abstracoes prematuras na preparacao multi-frontend","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","studio","frontend","architecture","multi-frontend","simplicity"],"agendas":[{"id":"AGD-0068","file":"AGD-0068-multi-frontend-avoid-premature-abstractions.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0064","status":"open","ticket":"multi-frontend-architectural-tests","title":"Testes arquiteturais para fronteiras multi-frontend","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","studio","frontend","architecture","tests","multi-frontend"],"agendas":[{"id":"AGD-0067","file":"AGD-0067-multi-frontend-architectural-tests.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0063","status":"open","ticket":"multi-frontend-synthetic-test-frontend","title":"Frontend sintetico de teste para provar neutralidade do pipeline","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","frontend","tests","backend","multi-frontend"],"agendas":[{"id":"AGD-0066","file":"AGD-0066-multi-frontend-synthetic-test-frontend.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0062","status":"open","ticket":"multi-frontend-pvm-neutrality","title":"Neutralidade da PVM e identificacao PBX independente de PBS","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["vm-arch","runtime","pvm","pbx","compiler","multi-frontend"],"agendas":[{"id":"AGD-0065","file":"AGD-0065-multi-frontend-pvm-neutrality.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0062","status":"done","ticket":"multi-frontend-pvm-neutrality","title":"Neutralidade da PVM e identificacao PBX independente de PBS","created_at":"2026-07-15","updated_at":"2026-09-18","tags":["vm-arch","runtime","pvm","pbx","compiler","multi-frontend"],"agendas":[],"decisions":[],"plans":[],"lessons":[{"id":"LSN-0061","file":"discussion/lessons/DSC-0062-multi-frontend-pvm-neutrality/LSN-0061-pbx-runtime-boundary.md","status":"done","created_at":"2026-09-18","updated_at":"2026-09-18"}]}
|
||||
{"type":"discussion","id":"DSC-0061","status":"open","ticket":"multi-frontend-sdk-canonical-definition","title":"Auditoria e centralizacao gradual da definicao canonica do SDK","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","sdk","stdlib","hostcalls","intrinsics","multi-frontend"],"agendas":[{"id":"AGD-0064","file":"AGD-0064-multi-frontend-sdk-canonical-definition.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0060","status":"open","ticket":"multi-frontend-validation-boundaries","title":"Separar validacoes de linguagem e validacoes de plataforma","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","compiler-pbs","backend","validation","multi-frontend"],"agendas":[{"id":"AGD-0063","file":"AGD-0063-multi-frontend-validation-boundaries.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0059","status":"open","ticket":"multi-frontend-common-lifecycle","title":"Extrair lifecycle comum das responsabilidades do frontend PBS","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","compiler-pbs","lifecycle","backend","multi-frontend"],"agendas":[{"id":"AGD-0062","file":"AGD-0062-multi-frontend-common-lifecycle.md","status":"open","created_at":"2026-07-15","updated_at":"2026-07-15"}],"decisions":[],"plans":[],"lessons":[]}
|
||||
{"type":"discussion","id":"DSC-0059","status":"done","ticket":"multi-frontend-common-lifecycle","title":"Extrair lifecycle comum das responsabilidades do frontend PBS","created_at":"2026-07-15","updated_at":"2026-09-19","tags":["compiler","compiler-general","compiler-pbs","lifecycle","backend","multi-frontend"],"agendas":[],"decisions":[],"plans":[],"lessons":[{"id":"LSN-0062","file":"discussion/lessons/DSC-0059-multi-frontend-common-lifecycle/LSN-0062-common-lifecycle-assembly-stage.md","status":"done","created_at":"2026-09-19","updated_at":"2026-09-19"}]}
|
||||
{"type":"discussion","id":"DSC-0058","status":"done","ticket":"multi-frontend-serializable-ir","title":"Manter a IR comum serializavel por design","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","ir","backend","serialization","multi-frontend"],"agendas":[],"decisions":[],"plans":[],"lessons":[{"id":"LSN-0060","file":"discussion/lessons/DSC-0058-multi-frontend-serializable-ir/LSN-0060-data-contract-first-for-serializable-irbackend.md","status":"done","created_at":"2026-07-15","updated_at":"2026-07-15"}]}
|
||||
{"type":"discussion","id":"DSC-0057","status":"done","ticket":"multi-frontend-frontend-backend-contract","title":"Estabilizar contrato entre frontend e backend comum","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","compiler-pbs","ir","backend","multi-frontend"],"agendas":[],"decisions":[],"plans":[],"lessons":[{"id":"LSN-0059","file":"discussion/lessons/DSC-0057-multi-frontend-frontend-backend-contract/LSN-0059-common-irbackend-handoff-and-backend-guardrails.md","status":"done","created_at":"2026-07-15","updated_at":"2026-07-15"}]}
|
||||
{"type":"discussion","id":"DSC-0056","status":"done","ticket":"multi-frontend-remove-pbs-branches","title":"Generalizar o contrato LSP/editorial para frontends","created_at":"2026-07-15","updated_at":"2026-07-15","tags":["compiler","compiler-general","compiler-pbs","studio","frontend","coupling","multi-frontend"],"agendas":[],"decisions":[],"plans":[],"lessons":[{"id":"LSN-0058","file":"discussion/lessons/DSC-0056-multi-frontend-remove-pbs-branches/LSN-0058-generic-frontend-editorial-contract-for-lsp.md","status":"done","created_at":"2026-07-15","updated_at":"2026-07-15"}]}
|
||||
|
||||
+143
@@ -0,0 +1,143 @@
|
||||
---
|
||||
id: LSN-0062
|
||||
ticket: multi-frontend-common-lifecycle
|
||||
title: Common lifecycle assembly after frontend declaration
|
||||
created: 2026-09-19
|
||||
tags: [compiler, compiler-general, compiler-pbs, lifecycle, backend, multi-frontend]
|
||||
---
|
||||
|
||||
# Common lifecycle assembly after frontend declaration
|
||||
|
||||
## Original Problem
|
||||
|
||||
`IRBackend` was already the common executable handoff, but the PBS frontend still
|
||||
owned two different jobs. It admitted language markers `[Init]`, `[Frame]`, and
|
||||
`InitAllowed`, and it also assembled the platform lifecycle: module init,
|
||||
project-init wrapper, published frame wrapper, physical entrypoint, and boot
|
||||
guard.
|
||||
|
||||
That second job discovered roles through `__pbs.*` names and lived inside
|
||||
`PBSFrontendPhaseService`. Another frontend could not reuse the boot sequence
|
||||
without copying PBS. Common backend code also risked treating PBS naming as the
|
||||
integration contract.
|
||||
|
||||
The old path had a concrete defect. The `[Init]` colocated with `[Frame]` is
|
||||
project init, but it was also included in the file-init fragment. The published
|
||||
wrapper then called module init and project init separately, so the same
|
||||
callable could run twice. Specs required project init exactly once, after all
|
||||
module initializers and before the frame root.
|
||||
|
||||
## Consolidated Decision
|
||||
|
||||
Declaration and assembly are separate.
|
||||
|
||||
An executable frontend emits an immutable, ordered, typed
|
||||
`IRLifecycleDeclaration` on `IRBackend`. The declaration carries:
|
||||
|
||||
- modules in explicit dependency order;
|
||||
- each module's ordered file-init fragment references;
|
||||
- an optional project-init callable;
|
||||
- exactly one frame-root callable.
|
||||
|
||||
References use `ModuleId`, `FileId`, `CallableId`, a typed role, and source
|
||||
attribution. Absence of a declaration means a deliberately non-executable
|
||||
handoff. It must not synthesize a default `main`.
|
||||
|
||||
`FrontendPhasePipelineStage` stops at that declarative backend.
|
||||
`AssembleLifecyclePipelineStage` runs immediately after it and is the terminal
|
||||
stage of `analyze()`. `LifecycleAssemblerService` is the only owner of derived
|
||||
lifecycle artifacts. `compile()` and `build()` reuse that single assembly pass.
|
||||
|
||||
`ResolveDepsPipelineStage` remains the ordering authority. Frontends propagate
|
||||
that order; the assembler validates and applies it. Neither side may rebuild
|
||||
order from synthetic names, `FileId`, textual module names, or incidental map
|
||||
order.
|
||||
|
||||
Project init is excluded from file-init fragments and runs exactly once. Common
|
||||
derived identities are neutral and deterministic. Common code must not import
|
||||
PBS packages or inspect `__pbs.*` prefixes. Typed roles, ids, and origins are
|
||||
the stable inspection surface; synthetic names are internal.
|
||||
|
||||
## Final Implementation
|
||||
|
||||
PBS now emits per-file lifecycle contributions and a project-level declaration.
|
||||
A colocated `[Init]` is the project-init reference only. File-init fragments
|
||||
remain frontend-lowered executables, consumed by id and role rather than by
|
||||
name prefix. `synthesizePublishedLifecycle` was removed.
|
||||
|
||||
The common assembler validates the declaration and materializes:
|
||||
|
||||
1. module init callables in declared module/file order;
|
||||
2. an optional project-init wrapper, invoked once;
|
||||
3. the published frame wrapper, which is the physical entrypoint;
|
||||
4. a hidden boot guard that prevents a second bootstrap after success.
|
||||
|
||||
The declaration remains on the assembled `IRBackend` as provenance. IRVM
|
||||
lowering keeps only assembled-graph preconditions such as wrapper identity,
|
||||
synthetic origin, and boot-guard presence. It does not reconstruct lifecycle
|
||||
from names.
|
||||
|
||||
`analyze()` still returns a fully assembled executable backend, without IRVM,
|
||||
bytecode, or file output. Neutral names use the `__prometeu.lifecycle.*` prefix.
|
||||
|
||||
Diagnostics stay split: PBS reports marker, signature, placement, cardinality,
|
||||
and colocation errors; the common layer reports unresolved ids, incompatible
|
||||
roles, missing frame root, invalid origins, and frontend-preassembled derived
|
||||
artifacts.
|
||||
|
||||
## Examples
|
||||
|
||||
Good frontend output:
|
||||
|
||||
- a file with globals or a non-project `[Init]` contributes a
|
||||
`FILE_INIT_FRAGMENT`;
|
||||
- the `[Init]` next to `[Frame]` is `PROJECT_INIT` only;
|
||||
- `[Frame]` is `FRAME_ROOT`;
|
||||
- module order follows the resolved dependency graph even when names or file
|
||||
ids would sort the other way.
|
||||
|
||||
Good assembled output:
|
||||
|
||||
- wrapper call order is module inits, then project init once, then frame root;
|
||||
- boot guard is a hidden global, not a user global;
|
||||
- `getLifecycleDeclaration()` still exposes the original typed references.
|
||||
|
||||
Bad output:
|
||||
|
||||
- PBS emitting `MODULE_INIT`, `PROJECT_INIT` wrappers, published wrappers, or
|
||||
boot guards;
|
||||
- common code matching `__pbs.frame_wrapper$m0` to discover the entrypoint;
|
||||
- sorting modules by `FileId` or textual path because the declaration order was
|
||||
inconvenient;
|
||||
- leaving both the PBS assembler and the common stage active.
|
||||
|
||||
## Pitfalls
|
||||
|
||||
- Do not treat `analyze()` as "frontend only." It now includes common lifecycle
|
||||
assembly so callers still receive an executable `IRBackend`.
|
||||
- Do not keep a temporary dual path. Two assemblers duplicate wrappers or init.
|
||||
- Do not infer missing frame roots or repair invalid declarations in the common
|
||||
layer. Fail deterministically.
|
||||
- Do not move PBS marker rules into the assembler. Language admission stays in
|
||||
PBS; structural handoff checks stay common.
|
||||
- Do not preserve `__pbs.*` names for common-derived artifacts as compatibility
|
||||
behavior. They were never a public ABI.
|
||||
- Do not confuse a frontend file-init fragment name with a common-derived
|
||||
identity. PBS may still name its own fragments; common code must not parse
|
||||
those names.
|
||||
|
||||
## References
|
||||
|
||||
- Decision: `DEC-0046`
|
||||
- Plan: `PLN-0125`
|
||||
- Related lessons: `LSN-0059`, `LSN-0060`
|
||||
- `docs/specs/compiler/23. Compiler Pipeline Entry Points Specification.md`
|
||||
- `docs/specs/compiler/20. IRBackend to IRVM Lowering Specification.md`
|
||||
- `docs/specs/compiler/22. Backend Spec-to-Test Conformance Matrix.md`
|
||||
- `docs/specs/compiler-languages/pbs/4. Static Semantics Specification.md`
|
||||
- `docs/specs/compiler-languages/pbs/9. Dynamic Semantics Specification.md`
|
||||
- `docs/specs/compiler-languages/pbs/12. Diagnostics Specification.md`
|
||||
- `docs/specs/compiler-languages/pbs/13. Lowering IRBackend Specification.md`
|
||||
- `prometeu-compiler/prometeu-frontend-api/src/main/java/p/studio/compiler/models/IRLifecycleDeclaration.java`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/main/java/p/studio/compiler/lifecycle/LifecycleAssemblerService.java`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/main/java/p/studio/compiler/workspaces/stages/AssembleLifecyclePipelineStage.java`
|
||||
+136
@@ -0,0 +1,136 @@
|
||||
---
|
||||
id: LSN-0061
|
||||
ticket: multi-frontend-pvm-neutrality
|
||||
title: PBX is the language-neutral runtime boundary
|
||||
created: 2026-09-18
|
||||
tags: [vm-arch, runtime, pvm, pbx, compiler, multi-frontend]
|
||||
---
|
||||
|
||||
# PBX is the language-neutral runtime boundary
|
||||
|
||||
## Original Problem
|
||||
|
||||
PBS was the first implemented frontend, so its name still appeared in a few
|
||||
common compiler specification titles. That editorial residue made it easier to
|
||||
misread the architecture as if PBS owned bytecode, IRVM, or the PVM execution
|
||||
model.
|
||||
|
||||
The implementation was already mostly neutral: the compiler emitted PBX, the
|
||||
runtime loaded PBX, and the common backend did not import PBS frontend packages.
|
||||
The real risk was future drift. In particular, IRVM could be mistaken for a
|
||||
runtime input, `PBS\0` could be confused with the executable magic, and duplicated
|
||||
VM-architecture documents could silently become competing authorities.
|
||||
|
||||
## Consolidated Decision
|
||||
|
||||
The executable pipeline is:
|
||||
|
||||
```text
|
||||
language frontend -> IRBackend -> IRVM -> PBX -> loader/verifier -> PVM
|
||||
```
|
||||
|
||||
`IRBackend`, `IRVM`, optimization, and PBX emission are compiler-owned.
|
||||
`IRVM` is an internal compiler representation and never crosses the runtime
|
||||
boundary. PBX is the only executable artifact consumed by the runtime.
|
||||
|
||||
The runtime repository owns PBX binary layout, Core ISA, loader behavior,
|
||||
verification, and PVM execution. Studio owns the common compiler transformations
|
||||
that produce conforming PBX. Studio copies of VM-architecture documents are
|
||||
mirrors, not independent authorities.
|
||||
|
||||
`PBS` names a language, frontend, stdlib, and explicitly language-specific
|
||||
integration. It does not name the executable format, magic, ISA, ABI, program
|
||||
image, or runtime type. The canonical persisted artifact is `program.pbx`, and
|
||||
its binary magic is `PBX\0`.
|
||||
|
||||
## Final Implementation
|
||||
|
||||
The common compiler specifications now identify bytecode/PBX and IRVM
|
||||
optimization as language-neutral surfaces. They explicitly state that IRVM is
|
||||
internal to the compiler and that PBX is the compiler/runtime boundary. Existing
|
||||
PBS references were retained where they describe legitimate frontend-specific
|
||||
publication or metadata behavior.
|
||||
|
||||
Studio's copies of `ARCHITECTURE.md`, `ISA_CORE.md`, and `INTRINSICS.csv` were
|
||||
synchronized with the runtime repository. A mirror policy now identifies the
|
||||
runtime repository as canonical and provides byte-for-byte comparison commands.
|
||||
|
||||
Existing Studio tests already proved two important invariants:
|
||||
|
||||
- `BytecodeModule` serializes the exact `PBX\0` header;
|
||||
- common backend contracts neither import nor publicly expose PBS frontend
|
||||
types.
|
||||
|
||||
Runtime conformance was strengthened in three focused places:
|
||||
|
||||
- the bytecode invalid-magic regression now explicitly proves that legacy
|
||||
`PBS\0` is rejected;
|
||||
- the PVM initialization regression now creates a `BytecodeModule` directly,
|
||||
serializes it, loads and verifies it, prepares the boot call, and executes it
|
||||
through `HALT` without any frontend;
|
||||
- a quality check inspects the `prometeu-bytecode` and `prometeu-vm` manifests
|
||||
and rejects dependencies whose identities belong to compiler or frontend
|
||||
layers.
|
||||
|
||||
No production VM behavior, ISA, ABI, or binary format changed.
|
||||
|
||||
## Examples
|
||||
|
||||
Language-specific work stops before the common backend:
|
||||
|
||||
```text
|
||||
PBS AST and semantic model
|
||||
-> PBS lowering
|
||||
-> neutral IRBackend data
|
||||
-> common IRVM lowering and optimization
|
||||
-> PBX\0
|
||||
```
|
||||
|
||||
A future frontend follows the same boundary:
|
||||
|
||||
```text
|
||||
FutureLanguage AST and semantic model
|
||||
-> FutureLanguage lowering
|
||||
-> neutral IRBackend data
|
||||
-> the same common IRVM and PBX stages
|
||||
```
|
||||
|
||||
The runtime sees the same PBX contract in both cases. It does not receive a
|
||||
`languageId`, source extension, AST object, IRVM object, or frontend service.
|
||||
|
||||
## Pitfalls and Anti-Patterns
|
||||
|
||||
- Do not expose IRVM as a convenient runtime protocol. It is optimized for
|
||||
compiler transformations, not binary compatibility or runtime loading.
|
||||
- Do not rename PBX concepts after the first frontend. `PBS\0` is invalid even
|
||||
when PBS produced the program.
|
||||
- Do not globally ban the word `PBS` from runtime documentation. PBS is a valid
|
||||
guest-language example; guards should inspect dependencies, public types, and
|
||||
format identities instead of raw text.
|
||||
- Do not duplicate tests when an existing guard proves the entire invariant.
|
||||
Extend coverage only for the missing distinction, such as explicit `PBS\0`
|
||||
rejection.
|
||||
- Do not let a documentation mirror become a second authority. Synchronize it
|
||||
against runtime or replace it with an explicit reference.
|
||||
- Loading a PBX image is not the same as beginning execution. The PVM boot test
|
||||
must prepare the published boot call before running the instruction budget.
|
||||
|
||||
## References
|
||||
|
||||
- `docs/specs/compiler/15. Bytecode and PBX Mapping Specification.md`
|
||||
- `docs/specs/compiler/20. IRBackend to IRVM Lowering Specification.md`
|
||||
- `docs/specs/compiler/21. IRVM Optimization Pipeline Specification.md`
|
||||
- `docs/vm-arch/README.md`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/main/java/p/studio/compiler/backend/bytecode/BytecodeModule.java`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/test/java/p/studio/compiler/specs/CommonBackendArchitectureTest.java`
|
||||
- Runtime: `crates/console/prometeu-bytecode/src/model.rs`
|
||||
- Runtime: `crates/console/prometeu-vm/src/virtual_machine.rs`
|
||||
- Runtime: `crates/dev/prometeu-quality-checks/tests/pvm_frontend_neutrality.rs`
|
||||
|
||||
## Takeaways
|
||||
|
||||
- PBX is the stable, language-neutral executable boundary.
|
||||
- IRVM stays private to the compiler pipeline.
|
||||
- Runtime authority and compiler authority are complementary, not competing.
|
||||
- Small dependency and artifact tests are enough to protect this boundary
|
||||
without introducing a plugin platform or a second language.
|
||||
@@ -1,77 +0,0 @@
|
||||
---
|
||||
id: AGD-0062
|
||||
ticket: multi-frontend-common-lifecycle
|
||||
title: Extrair lifecycle comum das responsabilidades do frontend PBS
|
||||
status: open
|
||||
created: 2026-07-15
|
||||
resolved:
|
||||
decision:
|
||||
tags: [compiler, compiler-general, compiler-pbs, lifecycle, backend, multi-frontend]
|
||||
---
|
||||
|
||||
# Agenda - Extrair o lifecycle do frontend PBS
|
||||
|
||||
## Objetivo
|
||||
|
||||
Domain owner: `compiler/general`, com impacto em `compiler/pbs`.
|
||||
|
||||
Separar declaracao de lifecycle feita por uma linguagem da montagem comum de init, frame, module initializers e entrypoint publicado.
|
||||
|
||||
## Contexto atual
|
||||
|
||||
As lessons e specs antigas indicam que PBS ja trata lifecycle e wrapper/entrypoint. O alinhamento pede que `PBSFrontendPhaseService` deixe de conter regras universais da plataforma.
|
||||
|
||||
## Escopo
|
||||
|
||||
- Localizar onde PBS sintetiza ou valida lifecycle.
|
||||
- Definir contrato comum de `LifecycleDeclaration` ou equivalente.
|
||||
- Planejar servico comum para validar, ordenar e montar entrypoint.
|
||||
|
||||
## Fora de escopo
|
||||
|
||||
- Alterar sintaxe PBS.
|
||||
- Mudar comportamento observavel de projetos existentes.
|
||||
- Refatorar todo o backend junto da extracao.
|
||||
|
||||
## Arquivos e componentes a inspecionar
|
||||
|
||||
- `prometeu-compiler/frontends/prometeu-frontend-pbs/...PBSFrontendPhaseService...`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/main/java/p/studio/compiler/backend/irvm/LowerToIRVMService.java`
|
||||
- `docs/specs/compiler/16. Runtime Execution and Initialization Specification.md`
|
||||
- `docs/specs/compiler/20. IRBackend to IRVM Lowering Specification.md`
|
||||
- `docs/specs/compiler-languages/pbs/13. Lowering IRBackend Specification.md`
|
||||
|
||||
## Alteracoes propostas
|
||||
|
||||
Opcao A: frontend PBS emite declaracoes neutras de lifecycle e backend/common assembler monta o entrypoint.
|
||||
|
||||
Opcao B: manter montagem no PBS por enquanto, mas isolar regras comuns em um servico compartilhado chamado pelo PBS.
|
||||
|
||||
Recomendacao inicial: extrair primeiro o servico comum com testes de caracterizacao, depois migrar o PBS para produzir apenas declaracoes.
|
||||
|
||||
## Estrategia de implementacao
|
||||
|
||||
Identificar fixture positiva atual, proteger com teste, criar contrato comum minimo, mover validacoes universais e manter mensagens PBS onde forem sintaxe/semantica da linguagem.
|
||||
|
||||
## Testes necessarios
|
||||
|
||||
- Lifecycle valido PBS continua gerando mesmo PBX/IRVM.
|
||||
- Lifecycle ausente ou frame invalido falha no nivel comum quando aplicavel.
|
||||
- Teste de IR comum com lifecycle sem parser PBS.
|
||||
|
||||
## Criterios de aceitacao
|
||||
|
||||
- PBS traduz a forma da linguagem para declaracoes neutras.
|
||||
- Servico comum valida e monta lifecycle da plataforma.
|
||||
|
||||
## Riscos
|
||||
|
||||
- Mover validacoes PBS-especificas para camada comum por engano.
|
||||
- Alterar ordem de inicializadores sem perceber.
|
||||
|
||||
## Decisoes que devem ser registradas
|
||||
|
||||
- Nome e ownership do servico comum.
|
||||
- Forma canonica das declaracoes de lifecycle.
|
||||
- Separacao entre erro de linguagem e erro de plataforma.
|
||||
|
||||
@@ -1,78 +0,0 @@
|
||||
---
|
||||
id: AGD-0065
|
||||
ticket: multi-frontend-pvm-neutrality
|
||||
title: Neutralidade da PVM e identificacao PBX independente de PBS
|
||||
status: open
|
||||
created: 2026-07-15
|
||||
resolved:
|
||||
decision:
|
||||
tags: [vm-arch, runtime, pvm, pbx, compiler, multi-frontend]
|
||||
---
|
||||
|
||||
# Agenda - Manter a PVM neutra
|
||||
|
||||
## Objetivo
|
||||
|
||||
Domain owner: `vm-arch`, com impacto em `compiler/general`.
|
||||
|
||||
Garantir que a PVM conheca apenas PBX/IRVM e conceitos runtime neutros, incluindo identificacao correta do formato como `PBX`/`PBX\0`, nao `PBS`.
|
||||
|
||||
## Contexto atual
|
||||
|
||||
O documento e focado no Studio, mas runtime neutrality e uma fronteira transversal. A PVM nao deve conhecer `PBS service`, `PBS struct`, `PBS optional` ou qualquer conceito de linguagem.
|
||||
|
||||
## Escopo
|
||||
|
||||
- Auditar nomenclatura e imports runtime/PVM disponiveis no repo.
|
||||
- Verificar magic/header de PBX quando o codigo estiver no workspace.
|
||||
- Confirmar que linguagem e convertida antes da execucao.
|
||||
|
||||
## Fora de escopo
|
||||
|
||||
- Modificar a PVM se o acoplamento estiver apenas no Studio ou compiler.
|
||||
- Alterar ISA sem necessidade.
|
||||
- Adicionar suporte a qualquer linguagem nova.
|
||||
|
||||
## Arquivos e componentes a inspecionar
|
||||
|
||||
- `docs/vm-arch/ARCHITECTURE.md`
|
||||
- `docs/vm-arch/ISA_CORE.md`
|
||||
- `docs/specs/compiler/15. Bytecode and PBX Mapping Specification.md`
|
||||
- `prometeu-compiler/prometeu-build-pipeline/src/main/java/p/studio/compiler/backend/bytecode/...`
|
||||
- runtime/PVM em repositorio ou modulo relacionado, quando presente
|
||||
|
||||
## Alteracoes propostas
|
||||
|
||||
Opcao A: auditoria documental e de codigo para nomes PBS indevidos em runtime/bytecode.
|
||||
|
||||
Opcao B: corrigir imediatamente apenas identificacao `PBS` vs `PBX` se houver bug confirmado e isolado.
|
||||
|
||||
Recomendacao inicial: auditar primeiro; corrigir somente caso a fronteira esteja claramente violada e a mudanca seja pequena.
|
||||
|
||||
## Estrategia de implementacao
|
||||
|
||||
Buscar termos PBS no runtime, bytecode e specs VM; classificar ocorrencias validas de docs historicas vs erros de contrato.
|
||||
|
||||
## Testes necessarios
|
||||
|
||||
- Teste de magic/header PBX.
|
||||
- Teste arquitetural impedindo imports PBS no runtime/PVM.
|
||||
- Teste de carregamento/verificacao de programa sem dependencia de linguagem.
|
||||
|
||||
## Criterios de aceitacao
|
||||
|
||||
- PVM nao depende de conceitos PBS.
|
||||
- Formato executavel e tratado como PBX.
|
||||
- Qualquer correcao runtime necessaria fica separada de refactors Studio/compiler.
|
||||
|
||||
## Riscos
|
||||
|
||||
- Confundir nomenclatura documental antiga com acoplamento real.
|
||||
- Expandir escopo para VM quando o problema pertence ao compiler.
|
||||
|
||||
## Decisoes que devem ser registradas
|
||||
|
||||
- Lista de conceitos permitidos na PVM.
|
||||
- Politica de nomenclatura PBX/PBS.
|
||||
- Onde ficam testes de neutralidade runtime.
|
||||
|
||||
Reference in New Issue
Block a user