https://alwaldend.com/docs/tools/rules_template/ Recent content in Rules template on Alwaldend Hugo en https://alwaldend.com/docs/tools/rules_template/openspec/specs/project-dns/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/tools/rules_template/openspec/specs/project-dns/spec/ <h1 id="project-dns-specification">project-dns Specification<a class="td-heading-self-link" href="#project-dns-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Record the retirement of <code>rules_template</code> landing infrastructure while preserving its reusable Bazel module.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-keep-landing-infrastructure-retired">Requirement: Keep landing infrastructure retired<a class="td-heading-self-link" href="#requirement-keep-landing-infrastructure-retired" aria-label="Heading self-link"></a></h3><p>The module SHALL follow the <a href="https://alwaldend.com/docs/tools/">tools boundary</a> and SHALL have no dedicated landing DNS declarations, Terraform root, or operational source exports.</p> <h4 id="scenario-inspect-the-module-after-landing-retirement">Scenario: Inspect the module after landing retirement<a class="td-heading-self-link" href="#scenario-inspect-the-module-after-landing-retirement" aria-label="Heading self-link"></a></h4><ul> <li><strong>WHEN</strong> the module is consumed from <code>tools/rules_template</code></li> <li><strong>THEN</strong> its reusable Bazel rules remain available without landing infrastructure.</li> </ul> https://alwaldend.com/docs/tools/rules_template/openspec/specs/project-rules-template/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/tools/rules_template/openspec/specs/project-rules-template/spec/ <h1 id="rules-template">Rules template<a class="td-heading-self-link" href="#rules-template" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Render Go text templates from declared data files through a command and a Bazel toolchain rule. This source baseline was observed on 2026-09-08 at revision <code>550d7e79b1f5fdbc2b6017b75178471d6914082f</code>. The command operates on one template and output per invocation; the rule&rsquo;s list attributes do not establish a multi-template rendering guarantee.</p> <p>Sources: <a href="https://alwaldend.com/docs/tools/rules_template/">project description</a>, <a href="../../../main/go/cmd.go">command flags</a>, <a href="../../../main/go/templater.go">templater</a>, <a href="../../../main/go/templater_func_map.go">template functions</a>, and <a href="../../../main/bzl/template_run_binary.bzl">Bazel action</a>.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-load-supported-data-formats-into-template-context">Requirement: Load supported data formats into template context<a class="td-heading-self-link" href="#requirement-load-supported-data-formats-into-template-context" aria-label="Heading self-link"></a></h3><p>The <code>template</code> command SHALL load data files in argument order into <code>DataFiles</code>, decode <code>.toml</code>, <code>.json</code>, <code>.ndjson</code>, and <code>.yaml</code> data, and expose <code>.txt</code> files as lines without structured decoding. <code>--extension</code> SHALL override extension selection for the supplied data files.</p>