Specify the Ansible-inspired template standard library in RFC 0006 (#596)

docs/contents.md

@@ -67,6 +67,15 @@ operator, user, and contributor references are easier to find.
   Application-owned configuration-load metrics, verbose snapshots, and bounded
   label vocabulary.
 
+## Proposals
+
+- [rfcs/](rfcs/): Requests for Comments proposing changes that need technical
+  review before they become binding.
+  - [rfcs/0006-ansible-inspired-template-standard-library.md](rfcs/0006-ansible-inspired-template-standard-library.md):
+    Survey of the ansible-core Jinja standard library, with an explicit
+    disposition for every candidate helper and Netsuke-native contracts for
+    the accepted set.
+
 ## User and operator guides
 
 - [quickstart.md](quickstart.md): First-run walkthrough for building with

docs/repository-layout.md

@@ -18,7 +18,8 @@ output and some leaf files so the long-lived structure remains visible.
 ├── cyclopts/
 ├── docs/
 │   ├── archive/
-│   └── execplans/
+│   ├── execplans/
+│   └── rfcs/
 ├── examples/
 │   └── hello-world/
 ├── installer/
@@ -68,6 +69,13 @@ output and some leaf files so the long-lived structure remains visible.
   after active roadmap work moves on.
 - `docs/execplans/`: Execution plans used as implementation handoff documents
   for scoped tasks.
+- `docs/rfcs/`: Requests for Comments proposing changes that need technical
+  review before they become binding, named `NNNN-short-topic.md` and numbered
+  in allocation order. Numbers are never reused, and are never renumbered
+  after publication. Gaps are therefore expected rather than erroneous: a
+  number may be reserved, drafted on another branch, or deliberately skipped,
+  so an unused number is not free for reallocation. Check every remote branch
+  for `docs/rfcs/` files before allocating one.
 - `examples/`: Example Netsuke manifests and minimal runnable sample projects.
 - `installer/`: Installer packaging assets and platform-specific packaging
   definitions.