Your website needs a considered policy for automated visitors
Search discovery, user-requested access and bulk collection are different questions for a publisher.
The Sansa journal
What technology makes possible. What it takes to make it useful. Perspectives on software, AI and robotics, grounded in the decisions teams face.
Public case study · Retrospective
A public incident case study: availability follows the dependency chain, not the architecture diagram.
Read the perspectiveJanuary 2025 — September 2026
42 articles · showing 12
Search discovery, user-requested access and bulk collection are different questions for a publisher.
A proposed platform project connecting editorial intent, traffic evidence and reversible access rules.
As voice moves into everyday work, the cost of an unnoticed misunderstanding becomes more visible.
A proposed mobile workflow that turns spoken observations into editable notes before they enter a system of record.
A public robotics case: adding ways to move also adds conditions to observe and evaluate.
A proposed Grasp-aligned concept focused on transitions, failed attempts and recovery observations.
Lower model costs do not remove the cost of exceptions, supervision and unfinished work.
A proposed assistant workflow with limits on time, tool use and the effort expected from reviewers.
The useful response to a broad AI announcement starts with a specific piece of unfinished work.
A proposed advisory project that ends with a testable brief and a clear boundary of authority.
Visual polish cannot tell a model which parts of a brand or customer journey matter most.
A proposed design project that tests a coherent page rather than collecting attractive isolated screens.
About this archive: two perspectives for each month, written as retrospectives and published on 22 September 2026. Case studies examine publicly documented work; future projects are proposed briefs, not announced products or completed client engagements.