<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>APPARATCHIK</title>
    <link>https://apparatchik.org/</link>
    <atom:link href="https://apparatchik.org/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Papers and agitprop concerning the administered life.</description>
    <language>en</language>
    
    <item>
      <title>Collection 14. Workforce Disruption Photographs, March–August 2026.</title>
      <link>https://apparatchik.org/papers/saaspocalypse/</link>
      <guid>https://apparatchik.org/papers/saaspocalypse/</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<div class="finding-aid">
  <div class="fa-front">
    <p>Photographer unidentified. Digital captures, various dimensions.</p>
    <p>Extent: 5 items (4 photographs, 1 printed matter).</p>
    <p>Transferred from the Office of Workforce Disruption upon dissolution.</p>
    <p>Access: open. Reproduction restricted.</p>
  </div>
  <ul class="fa-subjects">
    <li>SOFTWARE INDUSTRY — UNITED STATES — 2026</li>
    <li>DISPLACED PERSONS — TECHNOLOGY SECTOR</li>
    <li>ENCAMPMENTS</li>
    <li>SAAS COLLAPSE, 2026</li>
    <li>MIGRANT LABOR — REMOTE</li>
  </ul>
  <figure class="fa-plate">
    <img src="/assets/uploads/plate-01.png" alt="Tents crowded beneath a concrete interstate overpass. Laptops and small solar panels stand on milk crates outside the tents, two men warm their hands over a burning barrel, and a hand-lettered sign reads NO TRESPASSING, STANDUP AT 9AM SHARP.">
    <figcaption>Plate 1. Encampment beneath interstate overpass. Standup observed daily. Location unrecorded.</figcaption>
  </figure>
  <figure class="fa-plate">
    <img src="/assets/uploads/plate-02.png" alt="A man sits in the open doorway of a moving boxcar with a laptop on his knees and a phone beside him, rail line and mountains behind. Lettering beneath the photograph reads HOPPING THE 5G.">
    <figcaption>Plate 2. &ldquo;Hopping the 5G.&rdquo;</figcaption>
  </figure>
  <figure class="fa-plate">
    <img src="/assets/uploads/plate-03.png" alt="A man in a hat and worn coat, carrying a satchel, stands in the open doorway of an office beneath a sign reading PROSSER AND SONS BUSINESS TRANSFORMATION, SINCE 1934. A clerk in shirtsleeves and suspenders looks up from a ledger on the counter.">
    <figcaption>Plate 3. Applicant at the counter, Prosser &amp; Sons Business Transformation. The firm has since been acquired.</figcaption>
  </figure>
  <figure class="fa-plate">
    <img src="/assets/uploads/plate-04.png" alt="A man sits on the wooden steps of a clapboard house holding his hat, a rolling suitcase beside him, while a woman in an apron stands in the doorway behind him. Lettering beneath the photograph reads YOU GOT ANY PLATFORM WORK, MAAM?">
    <figcaption>Plate 4. &ldquo;You got any platform work, ma&rsquo;am?&rdquo;</figcaption>
  </figure>
  <figure class="fa-plate">
    <img src="/assets/uploads/item-05.png" alt="A folded, water-stained printed sheet headed A FIELD GUIDE TO MARKS OF THE WANDERING ENGINEER, with a grid of sixteen small drawn symbols, each with a short caption beneath it. The footer reads OFFICE OF WORKFORCE DISRUPTION, 2026.">
    <figcaption>Item 5. <em>A Field Guide to Marks of the Wandering Engineer.</em> Printed matter, one sheet, folded. Office of Workforce Disruption, 2026. Water damage.</figcaption>
  </figure>
</div>
]]></description>
    </item>
    
    <item>
      <title>Headcount 2026</title>
      <link>https://apparatchik.org/papers/headcount-2026/</link>
      <guid>https://apparatchik.org/papers/headcount-2026/</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>The Ministry reproduces below an item of correspondence received at this office. It is filed as received.</p>
<hr>
<p><strong>From:</strong> The Office of Registration, HEADCOUNT '26</p>
<p><strong>To:</strong> <a href="mailto:window3@apparatchik.org">window3@apparatchik.org</a></p>
<p><strong>Subject:</strong> Reminder: You are registered.</p>
<p>Your registration is confirmed. You are No. 04137.</p>
<p>You registered on a date you may not recall, at a partner event, at which you were scanned. Registration persists.</p>
<p>You have not yet attended. Attendance is the metric.</p>
<p><a href="https://headcount26.netlify.app/">CONFIRM ATTENDANCE</a></p>
<p><em>If you believe you received this message in error: you did not.</em></p>
<p>This message was sent to a counted address. To stop receiving reminders, attend!</p>
<hr>
<p><em>Filing note: Filed as received. The Ministry does not recall being scanned. The Ministry notes that this is consistent with being scanned.</em></p>
]]></description>
    </item>
    
    <item>
      <title>Meeting Decline Reason Codes — Quick Reference Card</title>
      <link>https://apparatchik.org/agitprop/decline-codes-quick-reference/</link>
      <guid>https://apparatchik.org/agitprop/decline-codes-quick-reference/</guid>
      <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Companion instrument to <a href="/papers/decline-codes/">APP-001, Meeting Decline Reason Codes</a>. Deployment: workstation, eye level. Retain at workstation. Do not remove.</p>
]]></description>
    </item>
    
    <item>
      <title>Meeting Decline Reason Codes</title>
      <link>https://apparatchik.org/papers/decline-codes/</link>
      <guid>https://apparatchik.org/papers/decline-codes/</guid>
      <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><strong>Choice List:</strong> <code>MTG_DECLINE_REASON</code><br>
<strong>Choice List Version:</strong> 2.2 <em>(unchanged)</em><br>
<strong>Document Revision:</strong> 2.2-b<br>
<strong>Status:</strong> Active<br>
<strong>Owner:</strong> Workplace Systems / Calendar Governance<br>
<strong>Applies to:</strong> All exempt and non-exempt staff, all regions<br>
<strong>Review cycle:</strong> Annual</p>
<hr>
<h2>1. Purpose</h2>
<p>This document defines the controlled vocabulary for meeting decline responses. Prior to v1.0, decline responses were free-text. Analysis of the free-text corpus found that 94% of declines resolved to some variant of &quot;conflict,&quot; which provided no actionable signal to organizers, capacity planners, or reporting.</p>
<p>Reason codes are mandatory on decline. Selection of a code is not an appeal and does not initiate review.</p>
<hr>
<h2>2. Key</h2>
<table>
<thead>
<tr>
<th>Symbol</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>†</strong></td>
<td>Comment required. Decline will not submit without free text.</td>
</tr>
<tr>
<td><strong>‡</strong></td>
<td>Not visible to organizer. Captured for reporting only; organizer receives a standard decline with no reason string.</td>
</tr>
<tr>
<td><strong>◦</strong></td>
<td>Excluded from decline-rate calculation.</td>
</tr>
</tbody>
</table>
<p>Symbols are cumulative. <code>PUR-14 †‡</code> requires a comment that the organizer does not receive.</p>
<p><em>Document Revision 2.2-b introduces this notation. No field behavior has changed. The flags were previously maintained in a separate section; consolidating them into the entry rows was requested at the v2.2 review after staff reported selecting codes without reference to their handling.</em></p>
<hr>
<h2>3. Choice List</h2>
<h3>CAP — Capability</h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>CAP-01</code></td>
<td>Capability exhausted — daily acts committed (3/3)</td>
</tr>
<tr>
<td><code>CAP-02</code></td>
<td>Decision budget depleted — weekly allocation spent</td>
</tr>
<tr>
<td><code>CAP-03</code> <strong>‡</strong></td>
<td>Judgment degraded — attendance would be nominal</td>
</tr>
<tr>
<td><code>CAP-04</code> <strong>‡</strong></td>
<td>Attention available, judgment unavailable</td>
</tr>
<tr>
<td><code>CAP-06</code> <strong>†</strong></td>
<td>Capacity present but non-transferable to this domain</td>
</tr>
<tr>
<td><code>CAP-07</code></td>
<td>Capability committed to work arising from prior meeting</td>
</tr>
</tbody>
</table>
<h3>PUR — Purpose</h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>PUR-11</code></td>
<td>No decision present in agenda</td>
</tr>
<tr>
<td><code>PUR-12</code></td>
<td>Decision present, decider absent</td>
</tr>
<tr>
<td><code>PUR-13</code> <strong>◦</strong></td>
<td>Agenda not published at time of response</td>
</tr>
<tr>
<td><code>PUR-14</code> <strong>†‡</strong></td>
<td>Outcome already determined prior to convening</td>
</tr>
<tr>
<td><code>PUR-17</code> <strong>‡</strong></td>
<td>Attendance requested for consent, not input</td>
</tr>
<tr>
<td><code>PUR-18</code> <strong>‡</strong></td>
<td>Stated purpose is visibility</td>
</tr>
<tr>
<td><code>PUR-19</code></td>
<td>Purpose is alignment; alignment already obtained</td>
</tr>
</tbody>
</table>
<h3>RED — Redundancy</h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>RED-21</code></td>
<td>Content available asynchronously</td>
</tr>
<tr>
<td><code>RED-22</code></td>
<td>Duplicate of standing forum</td>
</tr>
<tr>
<td><code>RED-24</code></td>
<td>Meeting exists to prepare for subsequent meeting</td>
</tr>
<tr>
<td><code>RED-25</code></td>
<td>Meeting exists to report on prior meeting</td>
</tr>
<tr>
<td><code>RED-26</code> <strong>‡</strong></td>
<td>Attendee overlap with prior instance exceeds 80%</td>
</tr>
<tr>
<td><code>RED-27</code> <strong>‡</strong></td>
<td>Third instance of same discussion in rolling 30 days</td>
</tr>
</tbody>
</table>
<h3>ROL — Role</h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>ROL-31</code></td>
<td>Role misidentified — attendee not accountable party</td>
</tr>
<tr>
<td><code>ROL-32</code> <strong>◦</strong></td>
<td>Accountable party identified; delegating</td>
</tr>
<tr>
<td><code>ROL-33</code> <strong>†‡</strong></td>
<td>Presence requested as quorum ballast</td>
</tr>
<tr>
<td><code>ROL-35</code> <strong>†‡</strong></td>
<td>Attendance requested for optics of representation</td>
</tr>
<tr>
<td><code>ROL-36</code> <strong>◦</strong></td>
<td>Required attendee list generated from distribution group</td>
</tr>
<tr>
<td><code>ROL-37</code> <strong>‡</strong></td>
<td>Invited in prior role; role no longer held</td>
</tr>
</tbody>
</table>
<h3>TIM — Time</h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>TIM-41</code></td>
<td>Conflicts with protected work — no defensive hold required</td>
</tr>
<tr>
<td><code>TIM-43</code> <strong>◦</strong></td>
<td>Outside contracted hours</td>
</tr>
<tr>
<td><code>TIM-44</code></td>
<td>Duration exceeds subject matter</td>
</tr>
<tr>
<td><code>TIM-45</code> <strong>‡</strong></td>
<td>Scheduled during recovery interval following prior act</td>
</tr>
<tr>
<td><code>TIM-47</code></td>
<td>Notice period insufficient to prepare stated contribution</td>
</tr>
</tbody>
</table>
<h3>OBL — Obligation Clarification <em>(acceptances)</em></h3>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>OBL-51</code> <strong>◦</strong></td>
<td>Accepting — no attendance implied</td>
</tr>
<tr>
<td><code>OBL-52</code> <strong>◦</strong></td>
<td>Accepting — no objection implied</td>
</tr>
<tr>
<td><code>OBL-53</code> <strong>◦</strong></td>
<td>Accepting — no endorsement of outcome implied</td>
</tr>
<tr>
<td><code>OBL-54</code> <strong>‡◦</strong></td>
<td>Accepting — capability will be drawn from another commitment</td>
</tr>
<tr>
<td><code>OBL-55</code> <strong>◦</strong></td>
<td>Accepting — attendance only, no contribution implied</td>
</tr>
</tbody>
</table>
<hr>
<h2>4. Usage Notes</h2>
<p><strong>4.1</strong> The <strong>‡</strong> flag was implemented in v1.4 following feedback that certain codes were being received as commentary.</p>
<p><strong>4.2</strong> All <code>OBL</code> codes carry <strong>◦</strong> because they are acceptances. They were introduced in v2.0 at the request of the Program Management Office to distinguish between the four things an acceptance had previously been taken to mean. A fifth was added in v2.2.</p>
<p><strong>4.3</strong> <code>CAP-01</code> requires no comment because the daily act count is derived automatically. Staff are not required to maintain the count manually and are advised not to.</p>
<p><strong>4.4</strong> <code>ROL-33</code> should be selected only where the requirement for quorum has been stated. Where quorum is unstated but inferred, use <code>ROL-35</code>. Both carry <strong>†</strong>.</p>
<p><strong>4.5</strong> <code>RED-26</code> is calculated at time of response and cannot be selected manually. It is applied by the system and appears in reporting as a staff selection. The <strong>‡</strong> flag applies to the system-applied value.</p>
<p><strong>4.6</strong> <code>CAP-07</code> was introduced in v2.2 after capacity planning observed that work generated by meetings was being declined under <code>TIM-41</code>, which classified it as protected work. It is not protected work. <code>CAP-07</code> allows the two to be distinguished in reporting.</p>
<p><strong>4.7</strong> No code carries all three flags. A code that is both comment-required and organizer-invisible is retained in the decline-rate calculation by design; the comment is the record.</p>
<p><strong>4.8</strong> There is no code for declining because the meeting should not exist. Requests for such a code have been received in each annual review since v1.2 and are logged under Enhancement Request <code>CAL-8817</code> (Backlog — Not Planned).</p>
<hr>
<h2>5. Deprecated Codes</h2>
<table>
<thead>
<tr>
<th>Code</th>
<th>Label</th>
<th>Retired</th>
<th>Flags at retirement</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>TIM-42</code></td>
<td>Conflict — other meeting</td>
<td>v2.0</td>
<td>—</td>
</tr>
<tr>
<td><code>PUR-15</code></td>
<td>Meeting is theater</td>
<td>v1.3</td>
<td>—</td>
</tr>
<tr>
<td><code>PUR-16</code></td>
<td>Meeting is theater (revised)</td>
<td>v1.4</td>
<td><strong>†‡</strong></td>
</tr>
<tr>
<td><code>CAP-05</code></td>
<td>Exhausted</td>
<td>v1.4</td>
<td>—</td>
</tr>
<tr>
<td><code>ROL-34</code></td>
<td>Not invited to the meeting where this was decided</td>
<td>v1.2</td>
<td>—</td>
</tr>
<tr>
<td><code>RED-23</code></td>
<td>Meeting exists because it exists</td>
<td>v1.3</td>
<td><strong>‡</strong></td>
</tr>
</tbody>
</table>
<p><strong>Retirement notes</strong></p>
<p><code>TIM-42</code> — Retired following Q3 finding that 71% of <code>TIM-42</code> selections masked capability constraints. Superseded by <code>CAP</code> series. Reporting continuity across the boundary is not guaranteed.</p>
<p><code>PUR-15</code> — Retired. Selection volume exceeded configured threshold.</p>
<p><code>PUR-16</code> — Reissued at v1.3 with <strong>†‡</strong> applied. Retired at v1.4.</p>
<p><code>CAP-05</code> — Retired at request of People Operations. Term determined to carry clinical implication. Superseded by <code>CAP-01</code>, which specifies the exhausted resource.</p>
<p><code>ROL-34</code> — Retired. Field was being used as a comment box.</p>
<p><code>RED-23</code> — Retired. Recurrence with no defined end date is a supported configuration.</p>
<hr>
<h2>6. Revision History</h2>
<table>
<thead>
<tr>
<th>Version</th>
<th>Change</th>
</tr>
</thead>
<tbody>
<tr>
<td>1.0</td>
<td>Initial release. 6 codes. Free-text field retained in parallel.</td>
</tr>
<tr>
<td>1.2</td>
<td>Free-text field removed. <code>ROL-34</code> retired.</td>
</tr>
<tr>
<td>1.3</td>
<td><code>PUR-15</code>, <code>RED-23</code> retired. <code>PUR-16</code> issued with <strong>†‡</strong>.</td>
</tr>
<tr>
<td>1.4</td>
<td><strong>‡</strong> flag introduced. <code>PUR-16</code>, <code>CAP-05</code> retired.</td>
</tr>
<tr>
<td>2.0</td>
<td><code>OBL</code> series introduced. <code>TIM-42</code> retired. Decline-rate calculation revised.</td>
</tr>
<tr>
<td>2.1</td>
<td><code>CAP-04</code>, <code>RED-27</code>, <code>TIM-45</code> added. No changes to calculation.</td>
</tr>
<tr>
<td>2.2</td>
<td><code>CAP-07</code>, <code>PUR-18</code>, <code>RED-26</code>, <code>ROL-37</code>, <code>TIM-47</code>, <code>OBL-55</code> added. No changes to calculation.</td>
</tr>
<tr>
<td>2.2-b</td>
<td>Document revision. Flag notation introduced (§2) and applied inline. No field behavior changed.</td>
</tr>
</tbody>
</table>
<hr>
<h2>7. Reporting</h2>
<p>The following reports are generated from this field and distributed on a monthly cycle:</p>
<ul>
<li>Decline Rate by Organization Unit</li>
<li>Top Decline Reasons by Organization Unit</li>
<li>Decline Rate by Individual (Manager view only)</li>
<li><code>CAP</code> Series Selection Frequency — Trailing 90 Days</li>
<li>Organizer Decline Exposure — Trailing 90 Days <em>(pilot)</em></li>
</ul>
<p>Reports draw on all selections regardless of <strong>‡</strong> status.</p>
<p>Sustained elevation in <code>CAP</code> series selection is surfaced to the reporting manager as a development indicator.</p>
<hr>
<p><em>Retain at workstation. Do not remove.</em></p>
]]></description>
    </item>
    
  </channel>
</rss>
