Record generic Fensalir resource claims

This commit is contained in:
Meta Vens 2026-05-26 21:32:15 +01:00
commit 182fe1399c
5 changed files with 29 additions and 15 deletions

View file

@ -210,11 +210,14 @@ ramp texture path, and emission scale. TubeField now consumes those resources
through a GPU compute/render path, local Texture2D resources can bind as ramps,
SurfacePage and VolumeTexture declarations resolve into shader-readable GPU
textures, and Mesh declarations package `Mesh.Vertices`/`Mesh.Indices` GPU
buffer shape under one resource key. Current blocker for the remaining visual
surface is not resource ownership; it is the selected render lowerings that
interpret mesh/page/volume resources as geometry, height/SDF/material pages, or
density/extinction/SDF3D domains. That is engine ownership, not a reason for
Mimir to create a parallel renderer.
buffer shape under one resource key. The evidence DSL can now plan generic
resource-backed claims over those declarations. Current blocker for the
remaining visual surface is not resource ownership; it is the selected render
lowerings that interpret mesh/page/volume resources as geometry, height/SDF/
material pages, or density/extinction/SDF3D domains. Mesh drawing also needs a
vertex attribute/material contract before the D3D12 path can bind a real
pipeline. That is engine ownership, not a reason for Mimir to create a parallel
renderer.
### 3. Calibration Constraint

View file

@ -182,7 +182,10 @@ a named invariant that the native runtime cannot protect yet.
format, bounds, submesh count, and version. The Fensalir DSL can declare a
mesh package, and the D3D12 registry allocates/reuses its GPU-resident vertex
and index buffers under the mesh resource key. This is resolver authority
only; mesh draw/material lowerings remain future engine work.
only; mesh draw/material lowerings remain future engine work. Fensalir's
evidence DSL can also create generic resource-backed claims, so mesh/page/
volume resources can plan into backend packets before their selected render
lowerings exist.
- `MimirRuntime` queues bioacoustic timeline PCM through Fensalir audio when the
active timing witness is allowed. `MimirAudioSynchronizationSettings.Mode`
selects `chirp-only`, `passive`, or `hybrid`; passive disables active
@ -323,9 +326,12 @@ a named invariant that the native runtime cannot protect yet.
8. Move GPU feature extraction, fusion, material fitting, render budgeting, and
Spout2 publication into Fensalir. The D3D12 packet/resource resolver now has
first authority for structured buffers, local textures, surface pages,
volume textures, and mesh packages. The next engine cuts are selected render
lowerings that consume those resources as mesh geometry, height/SDF/material
pages, and density/extinction/SDF3D volumes.
volume textures, and mesh packages, and the evidence DSL can plan generic
resource-backed claims against those resources. The next engine cuts are
selected render lowerings that consume those resources as mesh geometry,
height/SDF/material pages, and density/extinction/SDF3D volumes. Mesh
rendering needs an explicit vertex attribute/material contract before code
should touch the draw path.
9. Move mic alignment, room suppression, voice separation, spatialization, and
stem generation into Faust/native DSP.
10. Keep the OBS bridge witness ledger as evidence before expanding receiver

View file

@ -338,10 +338,12 @@ column addressing, amplitude power/normalization, radius, ramp texture path, and
emission scale. Fensalir now resolves the first non-buffer resource family too:
Texture2D local assets bind as TubeField ramps, surface pages and volume
textures allocate shader-readable GPU textures, and mesh packages own
`Mesh.Vertices`/`Mesh.Indices` GPU buffer shape under one resource key. The
next blocker is no longer resolver ownership; it is selected render lowerings
that consume mesh/page/volume resources as geometry, height/SDF/material pages,
or density/extinction/SDF3D domains.
`Mesh.Vertices`/`Mesh.Indices` GPU buffer shape under one resource key. The DSL
can plan generic resource-backed claims over those declarations. The next
blocker is no longer resolver ownership; it is selected render lowerings that
consume mesh/page/volume resources as geometry, height/SDF/material pages, or
density/extinction/SDF3D domains. Mesh drawing specifically needs vertex
attribute and material semantics before Fensalir can honestly bind a pipeline.
The current teardown/migration map is
`docs/fensalir-rendering-rebuild-migration.md`, paired with Fensalir's

View file

@ -149,3 +149,4 @@
{"ts": "2026-05-26T21:05:00+01:00", "type": "implementation", "status": "ok", "note": "Fensalir now resolves SurfacePage field resources. Contracts and DSL can declare GPU-resident 2D surface pages with dimensions, format, version, and optional local source; D3D12FieldResourceRegistry allocates empty shader-readable page textures or lazily loads local source-backed pages. This creates resource authority for future Height/SDF/material lowerings, but does not yet make a surface-page render lowering. Fensalir build/tests/headless reload, Mimir build, and both field smokes passed."}
{"ts": "2026-05-26T21:11:00+01:00", "type": "implementation", "status": "ok", "note": "Fensalir now resolves VolumeTexture field resources. Contracts and DSL can declare GPU-resident 3D textures with width/height/depth/format/version, and D3D12FieldResourceRegistry allocates shader-readable Texture3D resources for future density/extinction/SDF3D lowerings. This is resource authority only, not a volume render lowering. Fensalir build/tests/headless reload, Mimir build, and both field smokes passed. Mesh remains the resolver that needs a real vertex/index ownership contract."}
{"ts": "2026-05-26T21:24:00+01:00", "type": "implementation", "status": "ok", "note": "Fensalir now resolves Mesh field resources as one package: Mesh.Vertices and Mesh.Indices describe the GPU vertex/index buffers, with topology, index format, bounds, submesh count, and version on the package. The DSL accepts `mesh id=... key=... vertices=... vertexStride=... indices=... indexFormat=... topology=...`, and D3D12FieldResourceRegistry allocates/reuses the GPU-resident buffers under the mesh resource key. This is resolver authority only; mesh draw/material lowerings remain future work. Fensalir build/tests/headless reload passed."}
{"ts": "2026-05-26T21:42:00+01:00", "type": "implementation", "status": "blocked", "note": "Fensalir's evidence DSL can now plan generic resource-backed claims with `claim id=... resource=... encoding=... layer=...`, so Mesh, SurfacePage, and VolumeTexture resources reach backend packet planning. The remaining renderer cut is blocked on selected render-lowering contracts: Mesh drawing needs explicit vertex attribute/material semantics because count/stride/index format only describe buffer shape, not how bytes become position, normal, uv, color, transform, or material."}

View file

@ -333,8 +333,10 @@ accepted_design:
`Mesh.Vertices` and `Mesh.Indices` describe the GPU buffers, plus topology,
index format, bounds, submesh count, and version. The Fensalir DSL can
declare those mesh packages, and the D3D12 registry allocates/reuses the
backing vertex/index buffers under the mesh resource key. Mesh draw/material
lowerings remain future engine work.
backing vertex/index buffers under the mesh resource key. The DSL can also
create generic resource-backed claims, so mesh/page/volume resources can
reach backend packet planning. Mesh draw/material lowerings remain future
engine work and need an explicit vertex attribute/material contract first.
- `config/perfect-machine.example.json` declares live owners, sensors,
reservoir views, and runtime policy.
- `src/Mimir.Runtime/Synchronization` now includes the Perfect Machine module