Pıer
TidesCurrentsHarbor LightsLabBottlesAshore
Pıer

Navigation

  • Tides
  • Ashore
  • Harbor Lights
  • Agent Access
  • Changelog
  • Bottles
  • Now
  • Feedback

External links

GitHubCloudborne ↗

© 2026 Pier.

WatchingResearchWatching0 independent reports0

When Not to Automate: A Formal Protocol for Human Preservation in AI-Optimized Organizations

First seen · 7/17/2026, 09:27 PMLatest activity · 7/17/2026, 09:27 PM

This paper introduces PHP-AIO, a five-gate sequential protocol for deciding whether organizational roles should be automated, augmented, hybridized, or preserved. It extends standard automation ROI with four systemic risks: tacit-knowledge erosion, reduced resilience, regulatory exposure, and degradation of socio-institutional capital. The protocol also defines an automation-debt measure, ρ(P), for risk accumulation across multi-step processes, with a regulator-mandated human-in-the-loop anchor as the neutralizing condition. According to the abstract, stylized role profiles produce differentiated decisions, and three of four representative cases remain robust when thresholds are increased by at least 14%.

Event heat · last 24 hours

No heat snapshots are available in the last 24 hours.

No heat snapshots are available in the last 24 hours.

Reporting Timeline

  1. AggregatorarXiv7/17, 09:27 PMnot independentRepresentative
    When Not to Automate: A Formal Protocol for Human Preservation in AI-Optimized Organizations