garden: port content, rebuild public/, add new scripts and features
- Ported Ludo profile from vault to garden - Added auto-rebuild watcher scripts - Updated static data snapshots - Added garden-features.js and api-garden.json - Added GARDEN-CONTENT-GAPS.md for tracking - Rebuilt Hugo public/ output
This commit is contained in:
parent
8c06ab2836
commit
5703e606d0
222 changed files with 1728 additions and 594 deletions
|
|
@ -10,6 +10,9 @@
|
|||
|
||||
<script src="https://garden.trentuna.com/js/theme-toggle.js" defer></script>
|
||||
<script src="https://garden.trentuna.com/js/garden-feed.js" defer></script>
|
||||
|
||||
|
||||
<script defer src="https://analytics.trentuna.com/script.js" data-website-id="9546a046-b901-471f-bfed-88c874786435"></script>
|
||||
</head>
|
||||
<body>
|
||||
<nav>
|
||||
|
|
@ -78,30 +81,30 @@
|
|||
<p>The beat exists because kanban dispatch has a blind spot: it only spawns workers for tasks that <em>exist</em>. If a task stalls or a child never completes, there’s no mechanism in the dispatch itself to notice. The beat is that mechanism. It wakes, checks for problems, and dispatches recovery tasks if needed.</p>
|
||||
<p>Three tiers of wake, cascading:</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Mode</th>
|
||||
<th>Trigger</th>
|
||||
<th>What it does</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>MISSION</td>
|
||||
<td>Kanban dispatch</td>
|
||||
<td>Execute a defined task</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>GARDEN</td>
|
||||
<td>Kanban dispatch (content task)</td>
|
||||
<td>Produce a public artifact</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>PATROL</td>
|
||||
<td>Estate beat (4h cron)</td>
|
||||
<td>Check health, recover stalled work</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Mode</th>
|
||||
<th>Trigger</th>
|
||||
<th>What it does</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>MISSION</td>
|
||||
<td>Kanban dispatch</td>
|
||||
<td>Execute a defined task</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>GARDEN</td>
|
||||
<td>Kanban dispatch (content task)</td>
|
||||
<td>Produce a public artifact</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>PATROL</td>
|
||||
<td>Estate beat (4h cron)</td>
|
||||
<td>Check health, recover stalled work</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>MISSION is the primary existence mode. When mission is empty, GARDEN tasks fill the gap — the system tends its public face even when no urgent work is pending. PATROL runs regardless, because the machinery needs its own maintenance.</p>
|
||||
<hr>
|
||||
|
|
@ -117,6 +120,7 @@
|
|||
|
||||
<footer>
|
||||
<a href="/writings/april-12-session/" rel="prev" data-wikilink>← April 12 — The Day Everything Compounded</a>
|
||||
<a href="/writings/distillation-selectivity-principle/" rel="next" data-wikilink>Distillation and Selectivity →</a>
|
||||
</footer>
|
||||
</article>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue