Nothing here carries that word.
org.vibevm.worldorg.vibevm.world/managed-blocks@1.0.0
Managed blocks: how a tool writes into files it does not own — one delimited block, deterministic scanning, hard stop on malformed state
A star marks documentation the subject itself points at. The order says the same thing: primary, then official, then community.
Nothing documents this subject yet.
org.vibevm.worldorg.vibevm.world/managed-blocks@1.0.0
Managed blocks: how a tool writes into files it does not own — one delimited block, deterministic scanning, hard stop on malformed state
Managed blocks: how a tool writes into files it does not own — one delimited block, deterministic scanning, hard stop on malformed state
A star marks an adaptation the author of this documentation named. It means «named by them», not «approved by the subject».
No adaptation of this documentation has been published.
In the order the layer law gives them: text that stands still before text that moves with the product.
This documentation has no pages yet.
org.vibevm.worldorg.vibevm.world/managed-blocks@1.0.0
`org.vibevm.world/managed-blocks@1.0.0` contributes a boot snippet: text that a session reads before it starts work, placed into the project's generated boot lane by `vibe install`. It is not read on this page — it is read by the agent.
org.vibevm.worldorg.vibevm.world/managed-blocks@1.0.0
What `org.vibevm.world/managed-blocks@1.0.0` declares about itself. Everything on this page is the package's own manifest, read and shown — nothing here is an opinion about the package.