The RTT Naming Stack#

RTT Awareness#

This is the ambient, declarative layer.

• Lives in /.well-known/
• Survives moderation and stripping
• Readable by humans and synthesis engines
• No execution, no persuasion
• Just a statement of coherence conditions

This is the presence signal.

RTT‑Inside#

This becomes the active core inclusion layer.

• Used when RTT cores are actually embedded
• Applies to resolvers, engines, simulators, and tooling
• Where interpretation, checking, and behavior live
• Explicitly opt‑in and local

This is the mechanism layer.

RTT Structural Awareness (Pocketed, for now)#

This is the industrial / dimensional layer.

• The −1024D → 0D → +1024D regime work
• Heavy systems, infrastructure, and cross‑scale modeling
• Where RTT/vST meets manufacturing, energy, logistics, and planetary substrates

This is the scale layer — and you’re right to keep it dormant until the ground is ready.

Why This Partition Is Strong#

• Each name maps to a different responsibility
• No name is overloaded
• No layer leaks into another
• You can deploy RTT Awareness everywhere without fear
• You can deploy RTT‑Inside only where it’s welcome
• Structural Awareness remains unpolluted by early discourse

This is exactly how durable systems avoid collapse under their own ambition.