Gary FullerEnterprise content architecture

Index · Sheet A-04

Signals

Shorter observations, dated and deliberately unfinished. Most start on X as @fullermotion. Some of them grow into essays.

LegendLast signal 28 Sep 2026

Essay. Argued, edited, finished.

Signal. A dated first read.

Related essay. Where a signal was argued out in full.

May 2026 · showing 10 of 23

  1. Most companies are still thinking too small about AI agents.

    They see agents as task runners.

    Draft this.
    Summarize that.
    Create a ticket.
    Send a notification.
    Update a spreadsheet.

    Useful, but tactical.

    The bigger opportunity is agent orchestration: designing systems where agents participate in real enterprise workflows with governance, review, auditability, and human approval.

    That is not just automation. That is an operating model.

    It reduces repetitive work.
    It increases throughput.
    It protects brand, compliance, and process standards.
    It keeps humans in control where judgment matters.
    It creates repeatable leverage instead of one off productivity gains.

    At Fullermotion, this is the infrastructure layer we are focused on: orchestrated agents that solve enterprise problems at scale.

    The future of AI in business is not a random collection of copilots. It is governed, integrated, measurable agent infrastructure that lets teams spend less time moving work around and more time making better decisions.

    AI should not just make tasks faster.
    It should make the operating system of the business more intelligent.

    Full post on X

  2. Claude Opus 4.8 Is Moving Toward Better Judgment

    Anthropic released Claude Opus 4.8 on May 28, 2026, and the useful signal is not just another round of benchmark movement. The thing that stands out is more practical: the model appears meaningfully more honest about its own work.

    That matters in agentic development. A model can be impressive and still create drag if it papers over flaws, calls incomplete work done, or misses the errors it introduced while editing. The notable shift in Opus 4.8 is that it is reportedly far less likely than Opus 4.7 to let code flaws pass without comment. For anyone using Claude in coding agents or long-running engineering workflows, that is a quality-of-life improvement with real operational consequences.

    The second change worth watching is dynamic workflows in Claude Code. The direction is clear: more parallel work, more internal verification, and a stronger ability to carry codebase migrations from start to merge. That is not just a demo feature. It changes what it means to hand off a task to an AI coding system.

    There is also an economic piece. Fast mode is now cheaper than prior versions while running substantially faster. Lower cost and higher speed matter because agentic workflows are not single-prompt workflows. They involve exploration, edits, checks, retries, and review loops. When those loops get cheaper, more of the work can move into the background without requiring a special budget conversation every time.

    The version of this tool I want running behind me is not merely the one that writes more code. It is the one that has better judgment, catches more of its own mistakes, and can keep working without needing constant hand-holding. Opus 4.8 looks like a step in that direction.

    PermalinkFull post on LinkedIn

  3. Everyone is worried about the wrong developers.

    The conversation around tools like Codex keeps circling back to junior developers. That concern is not unreasonable. But it is aimed at the wrong level of the org chart.

    Understanding the problem and designing a solution made someone a good developer. Syntax mastery, the ability to translate that thinking into precise, idiomatic, production-ready code without friction, was what separated good from great. That fluency was the differentiator. It was what made a senior developer fast, reliable, and hard to replace.

    Codex just commoditized that differentiator.

    You are no longer writing the implementation. You are describing what correct looks like. The execution layer, the thing senior developers spent years sharpening, is no longer the constraint. The developers most exposed are not the ones still learning syntax. They are the ones who stopped at syntax.

    What survives is the capability that was always harder to teach and harder to hire for. Can you understand a problem with enough precision to define what a correct solution looks like before you see one? Can you articulate the goal clearly enough that someone, or something, else can execute without you in the loop at every step?

    That skill was always the ceiling. Most organizations never formally tested for it because execution speed covered for its absence. That path is narrowing fast.

    The developers who matter most in the next few years already understood that writing code was a means to an end. Everyone else has some recalibration to do.

    Full post on X

  4. Strapi, SvelteKit, and Railway can make a strong content platform. The stack is simple. The architecture still needs discipline: ownership, preview, promotion, rollback, permissions, and governance before quick exceptions become permanent patterns.

    Full post on X

  5. AEM Cloud raises the architecture bar. Managed infrastructure helps, but it does not fix weak content models, unclear permissions, or vague governance. Cloud reduces operational pain. It does not replace architectural discipline. Source: experienceleague.adobe.com/en/docs/experi…

    Full post on X

  6. AI agents are not magic productivity dust. They are force multipliers, but only when leaders structure the work: clear ownership, bounded responsibilities, useful context, repeatable workflows, escalation paths, and human approval where risk matters.

    Full post on X

  7. AI does not make AEM architecture less important. It makes weak architecture more expensive.

    Bad templates, vague metadata, inconsistent content fragments, and loose governance become fuel for faster confusion.

    AI scales systems. Make sure the system is worth scaling.

    Full post on X

  8. Worth checking out: Google Cloud’s Gemini Enterprise Agent Platform updates show where agents are headed. Revisions, skill registries, identity, gateways, and observability are controls for scale. docs.cloud.google.com/gemini-enterpr…

    Full post on X

  9. For my generation, the future we were promised as kids was spacefaring. It was “boldly go where no one has gone before.”

    SpaceX’s recent SEC filing is a reminder that this future is no longer just science fiction. Reusable rockets, orbital infrastructure, global connectivity, and a path beyond Earth are being built in real time.

    Humanity needs companies that expand the frontier, not just optimize the present.

    From that perspective, SpaceX is not just a company to admire. It is a company worth serious investor attention.

    SEC filing: Space Exploration Technologies Corp. S 1

    Full post on X

  10. Adobe’s Brand Visibility launch signals the shift: AI orchestration depends on governed content context across CMS, DAM, taxonomy, permissions, metadata, and approvals. Audit before scaling AI. news.adobe.com/news/2026/04/a…

    Full post on X