<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Implementation on Coyote Time</title>
    <link>https://blog.jonmikeys.com/tags/implementation/</link>
    <description>Recent content in Implementation on Coyote Time</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.jonmikeys.com/tags/implementation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 5: A Practical Tactical Awareness System, Starting Small</title>
      <link>https://blog.jonmikeys.com/posts/practical-tactical-awareness-system-starting-small/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/practical-tactical-awareness-system-starting-small/</guid>
      <description>A tactical awareness system should start small.&#xA;The first version does not need to model everything. It needs to answer one or two useful questions clearly.&#xA;Start with one signal The first step is to pick one tactical signal that is easy to measure.&#xA;Good candidates are:&#xA;visibility cover a small penalty for exposed paths The point is not completeness. The point is to get a result that changes behavior in a useful way.</description>
    </item>
  </channel>
</rss>
