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#

  • AnyAims (AA) Registry — 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.

  • DD — Design Decisions Registry — 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.