geb-protocol

AI self-location is achieved by applying a fractal, self-describing routing system with Root, Folder, and File metadata markers. This enables automated context collection and navigation without relying on global memory.

You can automate architecture documentation updates by using a self-healing workflow that triggers updates to I/O, Pos, _dir.md, and architecture references whenever structural changes occur in the project.

Fractal design for software architecture routing uses hierarchical metadata across roots, folders, and files to guide AI positioning and responsibilities, ensuring consistent context generation throughout the project.

Yes, the GEB protocol enforces explicit SKILL.md frontmatter along with _dir.md templates to establish the hierarchical markers required for AI to determine its position inside a project.

Creating a folder prompts the automatic generation of a _dir.md file containing Input, Output, and Pos templates, which provides the necessary context for AI navigation and responsibilities.

The best way to maintain context consistency is through a fractal self-describing marker system that auto-triggers scaffolding and self-healing updates to metadata whenever the project structure changes.