Mantle CWD Doctrine

Buf is the visible world

Buf is the singular interactive command line. The operator sees Buf prompts, Buf command input, and Buf output. In the abbrevinet style, a typed expression such as B:\ase\ is not treated as an ordinary Windows drive path by the operator-facing layer. It is a mantle expression that Buf interprets.

Symbiote is the hidden actuator

The PowerShell actuator lives in the OS/filespec world. It is not the visible command surface; it is the companion that performs the real media and folder work after Buf has translated the mantle expression. Buf talks to the Symbiote in lockstep, so the operator remains in the Buf world while the Symbiote handles the file-system world.

A mantle is two cooperating instances

An active mantle should be understood as a paired reality: the visible Buf side and the hidden Symbiote side. Buf is singular as the operator shell. Symbiote is activated for the Pinnacle when needed and owns the real drive/folder state that makes the mantle expression actionable.

Pinnacle activation

If a Buf command refers to B:\ase\, the B Pinnacle is the FireBase-oriented mantle world. If no Symbiote is active for that Pinnacle, one is born hidden. The command still appears as a Buf command, but the real execution is attached to the Symbiote for that Pinnacle.

Shared Symbiote, separate Buf shells

If another Buf shell refers to the same active Pinnacle, it does not create a second Symbiote merely because a second visible shell exists. The Symbiote is attached to the active mantle, not to the cosmetic fact of how many Buf windows are open. The real drive and folder truth lives with that Symbiote.

Translation rule

Buf translates abbrevinet mantle references for Symbiote. The operator may type a compact mantle expression, but Symbiote receives the resolved OS/filespec intent. This is why the earlier idea of showing a simple F: as the drive mantle was too flat: the mantle is not merely a drive letter. It is a Buf-visible expression bound to a hidden Symbiote actuator for a Pinnacle.

Canonical exposition for the Mantle Ecosystem

Every mantle carries its own cwd property. The :set and :get suffixes only control or reveal that cwd; all ordinary suffixes resolve relative to it.

Suffixes are not all the same

A property suffix continues a path inside the active mantle. A reserved usage suffix acts on the mantle itself. The contrast matters because B:\ase\docs describes a location, while a command form such as B:ase set or B:ase get is asking Buf and Symbiote to change or reveal mantle state.

In ordinary path use, Buf translates the visible mantle expression into the Symbiote's real OS/filespec context. In usage-suffix form, Buf recognizes a reserved operation and does not treat the suffix as a child folder. This keeps readable abbrevinet commands from being confused with physical paths.

Canonical identity

A canonized Mantle identity is a drive letter plus a canonical three-character suffix. Together, they form the Pinnacle of the Mantle. A form such as X:\mynose\readme.txt is not a Pinnacle unless it has been explicitly canonized.

Pinnacle and Primary Alias

The Pinnacle and Primary Alias address the same mantle. They are identical in usage. For example, a Mantle may be addressed by its compact Pinnacle or by its readable Primary Alias, while the Symbiote maintains the real physical drive and current directory.

Physical mapping

Each active mantle has a real physical location stored in the Pinnacles data table. By default, many physical locations normalize under C:\, but the Physical column is settable. Readers may always read the current mapping. Changes belong to the changer and must occur only at a safe spot, with no active connections.

Symbiote responsibility

When a mantle becomes active, its Symbiote is responsible for the actual OS/filespec current directory. Buf shows the mantle form to the operator; Symbiote stands at the real physical location. This is why Mantle identity is more than a drive letter: it is a canonized visible address bound to a hidden executor.

a google drive or onedrive has a physical file system prefix, for usage on that kind of drive, say google drive the starting 'root' would be normally like "G:\My Drive\" at startup default

• M:get returns a string only: the current cwd for mantle M. It does not copy, read, or inspect files.
• M:set accepts a path string only and changes the cwd for mantle M. It does not write files or move payloads.

• Each mantle starts at root with cwd = "\".
• Example: B:get -> "\" and therefore B:ase -> B:\ase\.

• If B:set receives "\somewhere\", then B:get returns "\somewhere\", and B:ase resolves to B:\somewhere\ase\.
• If the current cwd is "\somewhere\" and B:set receives "nowhere\", then B:get returns "\somewhere\nowhere\", and B:ase resolves to B:\somewhere\nowhere\ase\.
• If the current cwd is "\somewhere\nowhere\" and B:set receives "..", then B:get returns "\somewhere\".

For any mantle M, an ordinary suffix resolves as M:\<cwd>\suffix\. The suffix is always relative to the mantle's current cwd.

• A target such as D:evices\MotoAbcd may be instantiated on demand.
• On write: if the target folder does not exist, it is created and accepts the write.
• On read: if the target folder does not exist, reading it instantiates an empty directory.

The embodied directories are observable state surfaces. Subterranean FireDance can monitor their creation, removal, filling, and draining.

• Filenames carry visible key fields for indexing and watcher logic, for example: Init_TrackerA_SID4568098_GT02_Auto_...
• The file body carries fuller FireDance instructions and variables such as "SID4568098" !Init.Sid and "TrackerA" !Init.Id, along with any additional data that is too long or too private for the filename.

• Property suffixes: F:set, F:get, B:set, B:get, P:set, P:get. These affect mantle cwd state only.
• Embodiment suffixes: F:ire, G:ire, P:hos, B:devices, B:ase. These resolve to embodied directories relative to cwd.

• G:cld -> google cloud platform G:\cld\
• F:ire -> FireDance F:\ire
• P:hoSend -> PhoSend software P:\hoSend\
• D:evices -> Smart devices D:\evices\
• B:ase -> FireBase transport B:\ase\

Mantle is a filesystem-native operational language: mantles are drive syntaxed media locations, suffixes are relative embodiment points, cwd is the mantle focus, directories are observable route nodes, and files can be instruction carriers.