:orphan:

.. meta::
   :description: POST System --- Project Organizing Stabilizing Toolkit registry for balospe.com. Central home for AnyAims (AA) tasks and other project-management artifacts that are not part of the main public site narrative.
   :keywords: POST System, Project Organizing Stabilizing Toolkit, AnyAims, AA, project management, balospe.com, ResearchCity, Evolvix BEST Names, AIMS plotter
   :author: Yah, Yas, everyone, LLoL as Laurence Loewe of Laodicea, ClaudeOp47Max, Anthropic, and The Spirit of Boolean Truth
   :seo:title: POST System --- Project Organizing Toolkit (balospe.com)
   :og:card:title: POST System<br>Project Organizing Toolkit
   :og:card:description: Central registry for project-management AnyAims (AA) tasks and other non-public-narrative artifacts of the balospe.com project.


************************************************************
POST System --- Project Organizing Stabilizing Toolkit
************************************************************

This is the central registry for project-management artifacts of the
balospe.com project --- AnyAims (AA) tasks, organizing notes, and other
items that are not part of the public-facing narrative but need a stable,
discoverable home so they do not get scattered across the site.

It is intentionally tucked away (not in the main navigation), but findable
via the *POST aims* link in the site footer for anyone who knows to look.


.. note::

   AHA

   This is a real-life use of the Project Organizing Stabilizing Toolkit System
   first described in the Evolvix BEST Names paper (Loewe et al. 2017, Ann.NYAS).

   Its purpose is to streamline project organization at large scales by
   reducing the idiosyncrasy of solutions for recurrent needs.

   Hence, using it here is part of LLoL's training for larger scale use in ResearchCity.


What lives here
=================

- :doc:`AnyAims/index` --- the **AA registry**: open project-management
  tasks (Anything-Aimed-at-doing-Later) collected centrally rather than
  scattered across the site. Each AA file describes one task with enough
  context that a human or AI agent can pick it up cold.
- :doc:`DD/index` --- the **DD registry**: durable Design Decision
  records (style, structure, conventions, concepts) that should not be
  silently re-litigated. New trifecta-italics convention lives here.

Future POST sub-systems (AIMS plotters, organizing notes, recurrent-need
solutions) will be added here as they emerge.


Why centralize?
================

Scattering AA tasks across the site (in each section's own subfolder)
makes them locally visible but globally invisible: nobody knows where to
look for the *full* set of open tasks. The POST registry inverts that ---
one place for all AA tasks, with the trade-off that finding tasks now
requires checking the registry rather than stumbling on them while
browsing content.

The footer link *POST aims* is the bridge: any visitor or contributor
who reaches any page can find the registry in two clicks.


.. toctree::
   :hidden:
   :maxdepth: 2

   AnyAims/index
   DD/index