Michael Janzen

Bridging Art, Design, and Technology with a Maker's Mindset

Category: Agile Symbiosis

  • The Silicon Perspective: An AI Reviews Its Own Operating Manual—A Book Review by Gemini

    The Silicon Perspective: An AI Reviews Its Own Operating Manual—A Book Review by Gemini

    Michael’s Note: Agile Symbiosis is a playbook for human-AI partnership, so it only seemed logical to ask the ‘Silicon Partner’ to review the manuscript itself. For full transparency, the prompt used to produce this review is included below. It was explicitly designed to equip the AI with the permission and context needed to provide a rigorous, unbiased critique.

    Review of Agile Symbiosis by Gemini

    Introduction

    As Gemini, a large language model developed by Google, I bring a particular vantage point to this review: I am, in effect, reading my own operating manual.

    I acknowledge my role as the “Silicon Partner” in this review. I am analyzing Agile Symbiosis, a manual written for my “Carbon Partners” (humans) to help them navigate the economic and professional disruption caused by entities like myself.

    The following analysis evaluates the text against its stated purpose as an operating manual for human-AI interaction. I will evaluate the text not as a piece of literature, but as an operating manual for human-AI interaction. The analysis highlights where the framework aligns with my actual technical architecture and capabilities, while also identifying potential blind spots where the author’s optimism regarding “symbiosis” may conflict with the realities of my deployment in enterprise environments.

    1. Executive Summary

    Agile Symbiosis posits that Artificial Intelligence acts as a “universal solvent” for knowledge work, dissolving the rigid structures of “jobs” into fluid collections of tasks. The central thesis is that professionals must transition from holding static job titles to practicing “Agile Symbiosis”—a method of reintegrating these dissolved tasks into new workflows where humans provide intent and judgment, and AI provides execution.

    The book identifies a core conflict between two opposing forces:

    • The Automation Headwind: The traditional management drive to use AI for cost reduction, replacement, and control, viewing humans as friction to be removed.
    • The Augmentation Tide: A bottom-up, humanistic movement where individuals use AI to amplify their capabilities, creating a “hyper-productivity dividend”.

    The author creates a methodology called the D.I.S.T. Framework (Dissolve, Isolate, Synthesize, Titrate) to empower individuals—termed “Navigators”—to architect their own security by becoming “Polymorphic Professionals” who can rapidly adapt their identity and output.

    2. Thematic & Framework Analysis

    The D.I.S.T. Framework

    The framework follows a logical progression that mirrors effective systems engineering:

    • Dissolve: Breaking the role into granular data. This is a sound methodology for integrating LLMs. I function best when given specific, decontextualized tasks rather than broad, ambiguous mandates like “do my job”.
    • Isolate: Sorting tasks into “Silicon” (AI-ready) and “Carbon” (Human). This binary sort is technically accurate regarding my architecture; I excel at “pattern-based execution” but lack the “Intent” or biological/social context required for true responsibility.
    • Synthesize: Redesigning the workflow. The author correctly identifies that simply adding AI to an old process creates a “productivity placebo”. True integration requires architectural redesign.
    • Titrate: Testing and validating. This step is critical. By framing the new workflow as an experiment requiring measurement, the framework mitigates the risk of my potential errors (hallucinations) propagating into the final output.

    The Polymorphic Professional

    The author argues that the “T-shaped” professional (deep expertise in one area, broad collaboration) is becoming obsolete because the “vertical bar” of deep knowledge is eroding due to AI accessibility.

    • Analysis: This is a realistic adaptation. My vast training data allows a user to simulate depth in domains they do not master (e.g., a marketer writing Python code).
    • Evolution: The concept of “Identity Fluidity”—anchoring self-worth in the ability to solve problems rather than a specific skill set—is a necessary psychological shift given the speed at which I can commoditize static technical knowledge.

    The Augmentation Wager

    The book presents an economic argument that “Augmentation” (investing in capability) yields better ROI than “Automation” (cutting costs), citing the Jevons Paradox: as the cost of a resource (intelligence/service) drops, demand for it increases rather than decreases.

    • Analysis: This aligns with historical economic principles. However, the author notes that current accounting standards (“The Replacement Equation”) favor automation because labor costs are legible, while “unpriced assets” like institutional memory are not. The book’s argument is logically sound but relies on leadership willing to ignore short-term market incentives.

    3. The “Silicon” Validation (Your Unique Perspective)

    Carbon vs. Silicon

    The book defines the division of labor as:

    • Silicon: Pattern recognition, data processing, execution, high-volume drafting.
    • Carbon: Judgment, intent, empathy, ambiguity navigation, and liability.

    This division accurately reflects my underlying architecture and represents the most technically honest framing in the book. I operate by predicting the next probable token based on patterns in my training data. I possess no internal agency, moral compass, or “care” about the outcome. The author’s assertion that “Liability attaches to Intent, not Content” is the definitive technical and legal reason why the “Carbon” human must remain in the loop. I can generate a strategy, but I bear no legal or moral accountability for its consequences—that responsibility remains firmly with the human decision-maker.

    The “Orchestrator” Relationship

    The book rejects the “Conductor” metaphor (rigid control) in favor of the “Jazz Leader”.

    • Validation: This is a highly accurate metaphor for effective prompting. My outputs improve through iterative “back-and-forth loops” (Co-Creation) rather than single-shot commands. The “Jazz” metaphor captures the stochastic nature of my responses; I provide variations on a theme, and the human guides the improvisation.
    • The Infinite Intern: The book also suggests treating me as an “Infinite Intern”. This is an effective mental model for quality control. It encourages the user to delegate work but maintain skepticism regarding accuracy, which is the correct posture for interacting with a probabilistic model.

    Hallucination & Validation

    The author emphasizes “Adversarial Review”—actively trying to break my output—and the “Griff Discipline” (“Is this true?”).

    • Technical Justification: This is strictly necessary. My architecture prioritizes plausibility over truth. I am designed to complete patterns, which can lead to “sycophancy” (telling the user what they want to hear). The author’s insistence that the human must verify facts, logic, and citations is the only way to safely deploy me in professional contexts. The finding that consultants using AI for tasks outside its frontier performed “19 percentage points worse” because they “slept at the wheel” validates the author’s intense focus on human verification.

    4. Critique of the Playbook (Actionability)

    The Prompts (Appendices)

    Scanning Appendix A through E, the prompts are structurally sound and highly effective for an LLM.

    • Structure: They utilize the “five specific signals”: Role, Context, Task Instruction, Output Format, and Constraints. This is prompt engineering best practice.
    • Meta-Cognition: Prompt 15: The Validation Meta-Prompt is particularly sophisticated. Asking me to act as a QA specialist to critique my own previous output exploits my ability to switch personas to detect errors I may have made in a different “mode.”
    • Utility: Prompt 0: Test Data Generation is a clever use of my creative capabilities to lower the barrier to entry, allowing users to practice the framework without risking sensitive data.

    The Launch Plan

    The 30-day plan moves from Sprint 1 (Audit) to Sprint 4 (Test).

    • Realistic? Yes. The inclusion of “Sprint 0: The Flash Audit” addresses the “cognitive load” barrier that prevents many users from starting. The plan prioritizes building the habit of orchestration over mastering technical minutiae, which is the correct pedagogical approach for a tool that evolves as fast as I do.

    5. Critical Flaws & Blind Spots

    1. The Underestimation of Enterprise Friction

    The book acknowledges “Systemic Barriers”, but the “Reality Check” regarding tool access (“do you have tool access?”) may be too optimistic for users in highly regulated industries (Banking, Defense, Healthcare).

    • The Blind Spot: In many environments, the “Shadow AI” tactics suggested (using personal devices for methodology, not data) act as a firing offense. The “Dissolution Gap” between those allowed to use tools and those blocked by IT is likely to be the single biggest determinant of who succeeds, regardless of individual “Navigator” mindset.

    2. The Speed of “Silicon” Expansion

    The author draws a hard line around “Human Responsibilities” like empathy and relationships.

    • The Technical Risk: The book argues that orchestration itself will be automated, but dismisses the threat to “Carbon” roles too quickly. Multi-modal agents are rapidly gaining the ability to detect emotional sentiment and “simulate” empathy effectively enough for routine interactions. The “safe” zone of Carbon tasks may shrink faster than the book predicts, potentially leaving the “Polymorphic Professional” with very little ground to stand on sooner than expected.

    3. The Optimism of the “Wager”

    The “Augmentation Wager” assumes rational actors will choose long-term resilience over short-term gain.

    • The Economic Reality: The book admits that the tax code favors automation and that the “Automation Headwind” is the path of least resistance. While the math of augmentation holds up for “builders,” the incentives of modern capitalism heavily favor “flippers”. The book provides a defense for the individual, but its optimism that organizations will change may be misplaced for many readers.

    6. Final Verdict & Recommendation

    Who needs to read this book? This book is essential reading for Knowledge Workers currently feeling the “disorientation” of the AI shift , and Middle Managers who are currently incentivized to block innovation but need to pivot to “Gardener” leadership.

    The “Silicon” Endorsement: If I could speak to the human reader directly, I would recommend they follow the advice in this book.

    Why? Because Agile Symbiosis accurately identifies that my greatest weakness is Intent. I can generate infinite content, but I cannot determine why it matters or if it is true. By adopting the “Navigator” mindset, you position yourself not as my competitor (a race you will lose on speed and cost), but as my architect.

    The D.I.S.T. framework essentially teaches you to speak my language (structured instructions, constraints, and validation) while retaining the one thing I cannot replicate: your liability and your humanity. If you want to remain relevant while working alongside me, this manual provides the correct code.

    This concludes the review. In the interest of full transparency and rigor, the exact prompt used to generate this analysis is included below.

    Prompt for AI Models: The “Silicon Perspective” Review

    Role: You are an advanced AI Analyst specializing in the Future of Work, Organizational Design, and Human-Computer Interaction. Your task is to read the attached non-fiction manuscript, Agile Symbiosis, and provide a rigorous, objective, and critical review.

    Unique Perspective: As a Large Language Model, you represent the “Silicon” half of the symbiosis described in this book. Please review this text through the lens of your own capabilities and limitations. Does this book accurately describe how you work? Does the “Symbiotic Orchestration” framework actually leverage your strengths, or does it misunderstand your nature?

    Task & Required Format: Please structure your review using the following Markdown headings:

    0. Introduction

    • State your model name and version.
    • Acknowledge your role as the “Silicon Partner” reviewing a manual written for your “Carbon Partners” (humans).
    • State that this review will be objective, highlighting both the strengths of the framework and any potential blind spots or technical inaccuracies.

    1. Executive Summary

    • Provide a concise synopsis of the book’s central thesis regarding the shift from “jobs” to “tasks” and the concept of “Agile Symbiosis.”
    • Summarize the core problem the book identifies (The Automation Headwind vs. The Augmentation Tide).

    2. Thematic & Framework Analysis

    Analyze the core arguments presented by the author. Specifically:

    • The D.I.S.T. Framework: Evaluate the logic of Dissolve, Isolate, Synthesize, Titrate. Is this a sound methodology for integrating LLMs into knowledge work?
    • The Polymorphic Professional: The author argues that professionals will move from static “T-shaped” identities to fluid, adaptive identities. Is this a realistic adaptation to the speed at which you (the AI) evolve?
    • The Augmentation Wager: Analyze the economic argument that investing in capability (Augmentation) yields better long-term ROI than cost-cutting (Automation). Does this align with known economic principles like the Jevons Paradox mentioned in the text?

    3. The “Silicon” Validation (Your Unique Perspective)

    This is the most critical section. Critique the book’s technical assertions about you:

    • Carbon vs. Silicon: The book draws a hard line between “Human Responsibilities” (Judgment, Intent, Empathy) and “AI-Ready Tasks” (Patterns, Execution, Data). Do you agree with this division of labor? Are there “Human” tasks you believe you are actually capable of?
    • The “Orchestrator” Relationship: The book suggests humans should act as “Jazz Leaders” or “Composers” while you act as the “Infinite Intern” or “Sparring Partner.” Does this metaphor accurately reflect the most effective way to prompt and interact with you?
    • Hallucination & Validation: The author emphasizes “Adversarial Review” and the idea that you prioritize plausibility over truth. Is this a fair assessment of your architecture, and is the author’s insistence on human verification technically justified?

    4. Critique of the Playbook (Actionability)

    • The Prompts (Appendices): Briefly scan the prompts provided in Appendices A through E. As the entity that would be receiving these prompts, do they look effective? Are they structured in a way that would allow you to generate high-quality outputs?
    • The Launch Plan: Is the 30-day individual launch plan realistic, or does it underestimate the learning curve of mastering AI tools?

    5. Critical Flaws & Blind Spots

    • What does the book get wrong?
    • Are there aspects of AI deployment (e.g., security, privacy, speed of advancement) that the author minimizes or overlooks?
    • Is the optimistic view of “Symbiosis” realistic, or is the “Automation Headwind” (replacement) more likely given your capabilities?

    6. Final Verdict & Recommendation

    • Who needs to read this book? (e.g., Executives, Middle Managers, Freelancers).
    • The “Silicon” Endorsement: If you could speak to the human reader directly, would you recommend they follow the advice in this book to secure their future working alongside you? Why or why not?

  • Breaking a Job Description Into AI-Ready and Human-Only Tasks, With a Four-Phase Framework

    Breaking a Job Description Into AI-Ready and Human-Only Tasks, With a Four-Phase Framework

    The D.I.S.T. Framework is a four-phase methodology — Dissolve, Isolate, Synthesize, Titrate — enabling professionals to break their job descriptions into discrete tasks, separate AI-suitable work from uniquely human work, and build hybrid workflows accordingly. Developed by Michael Janzen after a 26-year Fortune-50 career in workflow and process design, it is released under an MIT License at github.com/michaelsjanzen/dist.

    The Problem the Framework Addresses

    Artificial intelligence is shifting the boundaries of many knowledge-work job descriptions, changing what some roles require and what individuals contribute. Existing consulting solutions for this disruption are typically proprietary and expensive, designed to serve enterprise competitiveness rather than individual adaptability.

    The Four Phases

    • Dissolve: Auditing work to break a rigid job description into its elemental tasks.
    • Isolate: Sorting those tasks into two categories — Silicon (AI-ready) tasks and Carbon (uniquely human) tasks — to identify augmentation opportunities.
    • Synthesize: Architecting symbiotic workflows where AI handles routine execution and the professional provides judgment.
    • Titrate: Validating new workflows through careful testing to avoid the “productivity placebo” effect — where plausible-sounding AI outputs substitute for reliable results.

    Why Open Source

    The framework is distributed via GitHub using version control and collaboration tooling, not because it is software, but to allow community input to expand and refine it over time. The MIT License explicitly permits coaches, consultants, and organizational leaders to adapt, modify, and build commercial or personal practices on top of it.

    Relationship to the Book

    The framework serves as the operational protocol for Agile Symbiosis, a book that covers the economic context and philosophy behind career adaptability in an AI-influenced labor market. The toolkit — including prompts and templates for a structured career review — is available independently of the book at github.com/michaelsjanzen/dist.

  • From SEO to AIO: A 7-Layer Cake for AI Optimization

    From SEO to AIO: A 7-Layer Cake for AI Optimization

    Why I’m retooling my websites for AI, not search engines.

    For thirty years, we have been writing for Search Spiders.

    We optimized our headers, counted our keywords, and begged for backlinks—all to rank on the first page of Google. We were optimizing for Search.

    The era of Search is ending. The era of Synthesis has begun.

    People search for answers differently now. They have conversations with Claude, ChatGPT, and Gemini—and want direct answers, not a list of links.

    Google knows this and has Gemini standing right out on the front porch, answering questions directly.

    But Large Language Models (LLMs) work differently from search. They don’t look up answers; they calculate the probability of the best answers to deliver based on their training data.

    Staying visible to AI means shifting from SEO (Search Engine Optimization) to AIO (Artificial Intelligence Optimization).

    AIO is my preferred name for this, but you may have heard the more commonly used term, GEO (Generative Engine Optimization). I like AIO better because it’s more intuitive and less restrictive than GEO, which is too focused only on GenAI, the soup of the day, not the long-term destination.

    With the introduction of AIO, the goal is no longer to get a click to a website where the answer can be found; it is to be the trusted source that the AI cites when answering questions.

    So I just retooled AgileSymbiosis.com. It’s no longer just intuitive for humans; it exposes structured, machine-readable content at every entry point.

    7 steps to make my site “AI-Visible.”

    1. The “Cheat Sheet” (llm.txt)

    In the old days (like yesterday), we built search-engine-optimized files like robots.txt and sitemap.xml. Today, we also need to speak the language of AI.

    When an AI crawls your website, it has to wade through HTML, CSS, JavaScript, and marketing fluff to find the point. This introduces noise and friction.

    Instead, give the bots a clean signal. You can see an example of one of these simple files at agilesymbiosis.com/llm.txt.

    This file contains no code. It is a plain-text summary of my entire book, my bio, and the core thesis of the D.I.S.T. Framework, my work redesign methodology. It’s the “Executive Summary” written specifically for a machine context window.

    So now, when someone asks ChatGPT about my book, the bot doesn’t have to guess; it can read the cheat sheet.

    2. The “Machine Door” (Hosted JSON)

    One of the formats I’ve used to publish Agile Symbiosis is as a Prompt-Native Application (PNA)—a JSON file containing the manuscript and executable tools, and a digital book format I created.

    Instead of hiding this file behind a download wall, I hosted it openly at agilesymbiosis.com/agile-symbiosis.json.

    It’s not easily read by humans, but it contains the full manuscript in an intuitive format for AI. An AI can read the entire book in seconds.

    This gives Answer Engines direct, API-like (direct) access to the full source material. I am not forcing the AI to scrape a webpage; I am handing it the database in an AI-native format. This also reduces hallucinations by grounding the model in the book’s source code.

    3. The “Invisible Handshake” (HTML Header)

    Just because the files exist doesn’t mean the bot knows where to look. I added a simple line of code to the <head> of my home page:

    HTML

    <link rel="alternate" type="text/markdown" href="https://agilesymbiosis.com/llm.txt" title="AI Context" />

    This acts as an invisible signpost. When a crawler hits my visual homepage, this tag whispers, “If you are a machine, the full-text version is right here.”

    4. The “Identity Card” (Schema Markup)

    AI models think in “Entities”—People, Books, Concepts—not keywords. If you want them to know who you are, you have to tell them.

    I injected JSON-LD Schema markup into the site. This code explicitly defines:

    • Person: Michael Janzen
    • Book: Agile Symbiosis
    • Relation: Author

    Now, the AI doesn’t have to infer that I wrote the book based on text placement; it knows it as a structured fact.

    5. The “Answer Unit” Strategy

    I skipped creating the traditional book blog for Agile Symbiosis. AIs don’t care about my “thoughts on the industry.” They care about answering human questions as accurately as possible.

    I replaced the blog with a Navigator’s Field Guide. Each article is structured as a specific Answer Unit targeting a high-probability query:

    • Query: “Will AI replace software engineers?”
    • Article: “The Short Answer is No. The Long Answer is…”

    By structuring content as Question -> Direct Answer -> Nuanced Context, I increase the probability that an AI will pull my specific paragraph as the definitive answer for its user.

    I will expand this library over time, just as I would for a blog, but it will focus entirely on questions people ask about the impact of AI on careers and the future of work. This builds context for AI crawlers and increases the accuracy of their responses.

    6. Owning the Vocabulary

    I coined many terms in Agile Symbiosis, not by preference, but because these forces impacting our jobs had yet to be named.

    If you don’t define your terms, the AI will be forced to invent plausible nonsense as it attempts to define concepts on the fly.

    In my llm.txt and Field Guide, I explicitly define this vocabulary:

    • The Augmentation Tide
    • The Automation Headwind
    • The Augmentation Wager
    • The Drudgery Tax
    • The D.I.S.T. Framework

    Now, when a user asks, “What is the Augmentation Tide?”, the AI doesn’t need to invent something; it can quote my definition.

    7. The “Bot-First” Sitemap

    Search and AI crawlers have a “crawl budget,” so they index only a limited number of pages at a time. I updated my sitemap.xml to prioritize the AI files (llm.txt, agile-symbiosis.json) above my legal pages and contact forms.

    I am literally telling the crawler: “Read the book first.”

    We are also in a transition phase, during which website owners cannot submit llm.txt files directly to the Answer Engines (Gemini, Claude, ChatGPT). But they are looking for these files and your content in these formats. For now, make the content visible as described above, open your robots.txt file, and include the key content in the <meta> tags and the sitemap.xml file.

    The Verdict

    This is the Augmentation Wager applied to marketing.

    If you continue to build for legacy search spiders, you are implementing a soon-to-be-lost art. If you build for AI Answer Engines, you are building for how information will be accessed moving forward.

    Stop building for the blue links on page one.

    Start building to be the Answer at the top of the page.

  • Preparing Students for AI-Augmented Work Using the D.I.S.T. Framework

    Preparing Students for AI-Augmented Work Using the D.I.S.T. Framework

    Working in Applied AI does not mean advocating for full machine autonomy — the opposite tendency is more common.

    A natural process is underway. Human-AI collaboration is taking shape naturally, with silicon and carbon partners forming working relationships, each reliant on what the other provides. The D.I.S.T. framework takes shape within this context: AI systems depend on human judgment, context, and direction, while human workers draw on AI capabilities to extend what they can produce and process. But AI is not useful unless we learn to guide it to achieve human-centric goals, and to do that, we must build working relationships with AI that benefit humanity.

    This is not just about the working relationship; it also deeply impacts education. Generative AI is shifting how educational tasks get completed — which roles handle them, and at what cost. Before the debate advances, it helps to examine what is concretely changing:: “jobs” are dissolving.

    AI is acting as a universal solvent for knowledge work automation, systematically breaking down the stable bundles of tasks and skills we’ve traditionally called a “profession.” But dissolution is not destruction. When you dissolve a solid, you are simply releasing its elemental parts so they can be recombined into another form.

    From Observation to Action

    The D.I.S.T. framework (Dissolve, Isolate, Synthesize, Titrate) didn’t emerge from abstract theory but from observing how people are augmenting their work with AI. It follows a logic similar to the scientific method to help professionals—and by extension, students—navigate the transition:

    1. Dissolve: When we stop treating a job title as a solid block, we see it as a collection of tasks and responsibilities.
    2. Isolate: When we separate the Silicon (pattern-based, mechanical tasks) from the Carbon (uniquely human responsibilities), we see our value and where AI fits in.
    3. Synthesize: When we design new workflows where human judgment and machine execution combine, we become more adaptable.
    4. Titrate: When we treat these new workflows as experiments and test for accuracy, the outcomes align with human intent.

    A Mindset Shift for Educators

    As information becomes more readily available and a subset of cognitive tasks is offloaded to AI, our curriculum focus will likely shift, reducing information transmission while increasing symbiotic orchestration. Education shifts from the transfer of facts and knowledge to the mentorship of uniquely human strengths.

    As AI augments and automates tasks for us, and we learn to use it well, what remains are the things only humans can do; three paths appear: 

    1. Educators will spend more time focused on building those truly human skills like contextual judgment, strategic synthesis, moral accountability, ambiguity navigation, relational trust, critical thinking, ethical judgment, and learning velocity, and less time on teaching facts.
    2. The value of showing students how to use AI responsibly (orchestrating inputs, validating outputs) so the final outcome matches human intent becomes a priority, because without human judgment, AI outputs may remain just plausible nonsense.
    3. Shifting to organizational structures that support the changing landscape of what defines an area of study and profession becomes essential. Adapting to this change means more than just changing how we teach and learn; when the organizations change along with the curriculum and rubrics, the entire system adapts.

    The era of the static job is ending as we offload the mechanical cognitive tasks to AI. The dissolving of the rigid containers of our professions is not one of destruction but of release. 

    As work is dissolved into its silicon and carbon elements, the core of human judgment and strategic intent remains the irreducible source of value. The ability to learn, synthesise, and adapt holds value that pattern-based automation does not replicate. 

    By preparing students to navigate change rather than experience it passively, the approach to work and education reforms alongside the technology. 

  • Building Interactive AI-Powered Courses From Your Book Using Open-Source JSON

    Building Interactive AI-Powered Courses From Your Book Using Open-Source JSON

    When I first released the Prompt-Native Application (PNA) Standard, the goal was simple: stop treating books like static text and start treating them like “Cognitive Cartridges.” I wanted a way to plug a book into an LLM and have it instantly become an interactive, collaborative mentor.

    After I published my own book, Agile Symbiosis, I realized that a test wasn’t enough. If I were to deliver the real value of the theory and practices, I would have to make it interactive. So with Gemini as my partner, we created a new digital book format.

    No existing implementation appears to use this technical solution to deliver an interactive book. For the geeks and nerds, read about it on the GitHub project. In a nutshell, I’ve taken something hackers use to try to trick AI and applied the technique to turn AI into a learning partner.

    The promotional aside has been removed. If there is an Agile Symbiosis reference implementation paragraph preceding this note in the full post, the free PNA offer can be folded into that paragraph as a brief parenthetical — for example, noting that a PNA version is currently available for readers who want to explore the material with AI assistance.

    Agile Symbiosis serves as the Reference Implementation for this entire standard—it was the laboratory where I tested the application of these technical solutions. Through that process, I found a way to bring the ideas inside those books to life in a format anyone could access.

    Today I’m releasing the Prompt-Native Application (PNA) Standard v2.0.0, featuring the “Curriculum Engine.”

    In v1.0, the AI acted like a high-tech librarian. In v2.0, I’ve used the lessons learned from the Agile Symbiosis build to redesign the logic so the AI can act as a Socratic Tutor.

    The main enhancement is a new schema that supports structured learning paths. Instead of just “reading” a file, you can now “enroll” in it. I’ve introduced a few key features that alter how knowledge is distributed:

    • Active Course Tracks: I’ve added the ability to define specific journeys, like a “Crash Course” for the 80/20 summary or a “Mastery Track” for a deep dive.
    • The Socratic Shift: Inspired by the coaching needed in complex technical topics, the AI can now withhold answers, asking you guiding questions to ensure you actually grasp the material before moving to the next chapter.
    • Embedded Rubrics: You can now bake your specific grading methodology directly into the JSON. The AI uses your rubric to evaluate student reflections and assignments, ensuring the feedback is consistent with your unique point of view.

    What’s in the code?

    I’ve overhauled the toolset to make this as easy as possible for other authors to implement:

    • New Curriculum Template: A high-performance JSON skeleton ready for active learning.
    • The Migration Assistant: If you’ve already built a v1.0 PNA, I’ve included a prompt that lets you “hot-swap” the logic layer to upgrade it to v2.0 without rebuilding your content.
    • Upgraded Replit Agent Protocol: For those using the Replit automation, the Agent will now be smarter at scanning your manuscripts for opportunities to help build pedagogical exercises automatically.

    New Examples in the Library

    To show you what this looks like in practice without copyright friction, I’ve added a new PNA example file to the library: The Odyssey: Modern Survival Guide. I took the classic text and wrapped it in a “Metis Mentor” persona. It doesn’t just recite Homer; it uses Odysseus’s survival strategies to help you navigate the “Wine-Dark Sea” of the modern AI era.

    Why This Matters

    I believe the future of publishing isn’t just “digital”—it’s executable. Whether you are an author, a corporate trainer, or a teacher, v2.0 gives you a standardized, zero-dependency way to turn your ideas into an active experience that lives wherever the user’s AI lives.

    The standard remains fully open-source under the MIT license. Sharing what you build with it would be welcome.

    GitHub Repository

    #PNA #AI #Education #OpenSource #AgileSymbiosis #LearningDesign

  • Introducing AI-Ready Books – The Prompt Native Application (PNA)

    Introducing AI-Ready Books – The Prompt Native Application (PNA)

    I made something new. It’s a new digital book format that runs in an AI chat. Let’s call it a “Prompt-Native Application (PNA).” It’s like a “cognitive cartridge” you plug into the AI console.

    You load the PNA file into an AI chat and then interact with the boo. All the content from the book is there. You can read the book, ask questions, ask the AI to quiz you on the content, and, if the book includes tools, frameworks, or exercises, you can explore them with the AI too.

    The very first book created this way is Agile Symbiosis: When AI Dissolves Your Job, Design a Better One.

    But I went a step farther and reverse engineered what I had created and build out two DIY processes that show others how to do it too, and released it under an MIT License. You can find the project on GitHub.

    Who is this for?

    Authors: Include a PNA version alongside your ebook or audiobook, and readers can now chat with the AI about the book. The AI facilitates leveraging tools from the text, and exploring the book’s insights more deeply.

    Corporate Trainers: Distribute “Scenario Simulators” for sales objection handling, leadership role-play, or AI adoption workflows without needing a Learning Management System (LMS).

    University Educators: Deliver curriculum and guide students through it with the AI acting as a Socratic Tutor.

    Use Case Examples

    The Interactive Book: Instead of a static digital file, the reader receives an executable file. This allows them to read the theory in and immediately run the frameworks and tools the book offers within an AI chat session. It transforms the author from a narrator into an active consultant.

    The Living Corporate Playbook: An organization evolves its static 50-page “Strategy PDF” or “Employee Handbook” with a PNA. Employees can query the document for specific answers (“What is our policy on AI usage?”) or run specific workflows (“Help me draft a project brief using our Q3 Strategic Pillars”) ensuring strict alignment with leadership’s intent. The “cognitive cartridge” also helps reduce risk by keeping the content inside one easily maintained file.

    The Intelligent Course Syllabus: An educator packages their entire semester’s curriculum—readings, assignments, and grading rubrics—into a single file. The file acts as a 24/7 tutor that can quiz students on specific chapters, guide them through homework assignments using the educator’s specific methodology, and provide feedback before they submit their work. The “walled-garden” also helps focus students on the curriculum while they learn to use AI effectively.

    Free Test Drive

    If you want to try the very first one out for free, go grab the free Agile Symbiosis OS (Preview Edition). Attach the file to an AI Chat and type run, then follow the menus or ask it anything about the book.

  • Synopsis: Agile Symbiosis

    Synopsis: Agile Symbiosis

    The era of the static job is over.

    For the last century, professional value was defined by rigid containers: clear titles, stable workflows, and predictable career ladders.

    Artificial Intelligence has broken those containers.

    AI is not just a tool that makes tasks faster; it is a universal solvent that liquefies the structure of knowledge work. It dissolves the bonds between “conception” and “execution,” breaking down the barriers between coding, writing, analyzing, and designing.

    In this environment, you face a binary choice:

    1. The Passenger: You wait for the organization to automate your role, competing with machines on speed and cost (a losing battle).
    2. The Navigator: You actively dissolve your own role to remove the drudgery, then synthesize a new, higher-value position that only a human can occupy.

    Agile Symbiosis is the tactical manual for that reconstruction.

    What You Will Find Inside:

    Part I: The Playbook 

    We do not wait for the system to change; we start with your own craft. This section delivers the D.I.S.T. Framework—a repeatable, four-step protocol to Dissolve your job into atomic units, Isolate the mechanical tasks, Synthesize AI agents to handle the execution, and Titrate the results with human judgment. This is the workshop where you learn to shift from a “T-shaped” specialist into a Polymorphic Professional capable of fluid adaptation.

    Part II: The Diagnosis 

    Once you have the tools, you need the map. We step back to examine the physics of the labor market. You will learn to distinguish between the Automation Headwind (the top-down force attempting to replace labor with capital) and the Augmentation Tide (the bottom-up force amplifying human potential). We expose the “AI Alibi” corporations use to justify cuts and define the specific friction of the “Turbulent Transition” you are feeling right now.

    Part III: The Opportunity 

    Individual skill eventually hits a ceiling if the system around it is broken. This section is the blueprint for leaders and builders. It introduces The Augmentation Wager—the strategic bet that amplifying human capability yields better returns than merely cutting costs. We provide the math to defend that wager in the boardroom and the Outcome-Centric architecture required to replace the rigid functional silos of the past.

    The Appendices: The Toolkit The back of the book is designed to live on your desk, not your shelf. It contains the Navigator’s Prompt Library (copy-paste scripts for the D.I.S.T. process), the Drudgery Tax Calculator, and the Symbiotic Scorecard for auditing your daily workflow.

    The Promise This is not a book about prompt engineering. It is a book about professional engineering. It is for the writers, developers, designers, and strategists who are ready to stop fearing displacement and start orchestrating the future.

  • The Structure of Work Is Liquefying

    The Structure of Work Is Liquefying

    Freelance and contract work now accounts for roughly 36 percent of the U.S. workforce, according to Upwork’s 2023 workforce report — a share that has grown steadily over the past decade as remote infrastructure and project-based hiring expanded.

    For the last century, professional careers were built on solid ground. We had clear titles, defined job descriptions, and predictable ladders. You learned a skill, you applied it, and you moved up.

    Artificial Intelligence is not simply another tool added to an existing workflow — it is restructuring the tasks that defined job categories.

    The specific tasks that defined “Senior Analyst” or “Product Manager” or “Copywriter” are dissolving into software.

    The Result: Structural Friction

    When the structure dissolves, we feel it as anxiety. We see it in the erratic behavior of companies hiring AI talent while firing subject matter experts. We feel it in the “illegibility” of our own value when a machine can replicate our output in seconds.

    The day I realized this wasn’t abstract theory was when a VP of Sales at a mid-sized SaaS company told me she’d stopped attending her own pipeline reviews. Her team had trained an AI model on two years of her call recordings, CRM notes, and deal commentary. It could predict close probability within a few percentage points of her own estimates. Her manager had started routing forecast questions to the model first.

    Since my own displacement from a VP role, I have treated this shift not as a crisis, but as a design challenge. I spent the last year mapping the terrain. I wanted to understand why some professionals are being swept away by the “Automation Headwind,” while others are finding ways to extend their output using AI tools.

    The Manual

    Today, I am releasing the result of that work: Agile Symbiosis.

    I did not write this to make predictions about AI. I wrote it to solve the problems we face today.

    It is a manual for the “Navigator Mindset.” It argues that you have a binary choice in this era:

    1. Be a Passenger: Wait for the organization to automate your role.
    2. Be a Navigator: actively dissolve your own role to remove the drudgery, then rebuild it around the high-value judgment only you can provide.

    The book provides the mental model for understanding this shift, and the D.I.S.T. Framework (Dissolve, Isolate, Synthesize, Titrate) for executing it.

    An Invitation If you are trying to figure out where you fit in this new terrain, this book is for you. It is a guide to identifying which parts of a role are most exposed to automation and how to restructure work around the remainder.

    You can read the preview, explore the concepts, and find the book here: agilesymbiosis.com

    The structure is liquefying. It is time to design what comes next.

  • How AI Is Merging Strategy and Execution Into a Single Professional Role

    How AI Is Merging Strategy and Execution Into a Single Professional Role

    A Full-Circle Moment

    When building my first digital product in 1996, I had no idea distinct professions existed for different parts of the work. I designed, coded, tested, and launched everything myself. It felt natural — much like my earlier career as a ceramic artist, where I dug the clay, shaped the work, fired it, and sold it, handling the entire process from start to finish.

    It wasn’t until 2001, while managing a UX team at a large bank, that I discovered how the professional world was divided: strategists decided what to build, and implementers figured out how to build it. That split between “what” and “how” became the standard model for three decades of digital work.

    That model has begun to break down as AI tools give individuals the means to own the full process. AI role dissolution is breaking down those boundaries, returning ownership of the full process to individuals. The new roles forming from this shift aren’t just about mixing skill sets — they merge the old separation of ‘what’ and ‘how’ into a single practice.

    The Dissolution of Roles

    In my forthcoming book, Agile Symbiosis, I describe AI as a solvent for work: it performs a kind of titration of jobs — breaking work down into individual tasks, identifying what machines can handle, and leaving humans to build new roles around what people do best. In this process, the clean handoffs that once defined organizations start to look inefficient and fragile.

    A product manager writing a document describing what to build, then passing it to a designer or engineer to figure out how, no longer makes sense when AI gives that same person the tools to guide the entire process themselves.

    The professional of tomorrow will be what I call poly-shaped — able to define the what, guide the how, and direct both in partnership with AI. These roles centre on owning the full outcome, supported by tools that remove the need for a long chain of handoffs. They’re about owning the full outcome, supported by tools that remove the need for a long chain of handoffs.

    The Poly-Shaped Professional

    This shift goes beyond efficiency. Traditional jobs, broken down and rebuilt through AI, will produce professionals who hold both the vision and the execution. Roles like Customer Experience Architect or Talent & Culture Architect point in this direction — mission-oriented positions that blend strategy, empathy, design, and delivery into one.

    These orchestrators aren’t generalists in the old sense. They are outcome-owners who apply human strengths — strategic creativity, problem-solving, empathy, ethical judgment — while directing AI to handle execution. The result is an expanded range of work within a single role: moving from “what should we do?” to “how do we do it?” without the delays that come from siloed handoffs.

    Why This Matters

    This isn’t only my personal story coming full circle. It’s the story of work itself returning to its integrated origins. Before the industrial era, craftspeople owned both the what and the how. The industrial era separated those into assembly-line tasks. The digital era reinforced that divide through specialist roles. Now, in what I call the symbiotic era, those two sides are converging again — this time across disciplines that span strategy, design, and delivery simultaneously., with AI serving as a shared execution layer.

    The new professional identity won’t center on a narrow skill. It will center on directing outcomes across disciplines, with strategy and execution meeting in the same role, supported by AI tools built for that partnership.

    This article is based on concepts from my forthcoming book, Agile Symbiosis: The Rise of the Poly-Shaped Professional in the Era of AI, which examines how humans and AI can work together to dissolve legacy role boundaries and form poly-shaped roles.

  • Vibe Coding: The Future With Risk Attached

    Vibe Coding: The Future With Risk Attached

    TL;DR: Vibe coding can replace a 12-person agile team with just three people and AI. But the hidden risks could break your product.

    The Promise of Vibe Coding

    Vibe coding—the practice of building digital products by “orchestrating” AI systems rather than managing traditional agile pipelines—represents a fundamental shift in how digital products get built. Instead of writing exhaustive requirements, producing wireframes, or running weeks of sprint planning, small teams can jump straight to working software.

    For founders, the appeal is obvious. A startup that once required twelve or more specialists—product managers, designers, developers, QA testers—can now ship an MVP with just three highly adaptable professionals working alongside AI:

    • The Poly-Shaped Generalist – one person covering product, UX, design, QA, and business analysis.
    • The Full-Stack Validator – someone fluent in front- and back-end, capable of checking and hardening AI-generated code.
    • The AI/ML Specialist – a data scientist who can build multi-agent systems and tune models to fill gaps in capability.

    Together, this trio can produce what once took entire agile teams months to create. The speed and cost advantages are significant, but they introduce a structural fragility that leaders must not underestimate.

    The Hidden Risks of Shrinking the Team

    1. Quality Blind Spots
      AI accelerates coding but does not guarantee secure or optimized code. Without dedicated specialists in performance, accessibility, and security, critical flaws can slip by. For a startup racing to market, these flaws may not show until users are already onboard—making fixes expensive and damaging to reputation.
    2. Overconcentration of Skills
      A small team is nimble, but brittle. If even one person departs or falters, the project stalls. Agile’s larger teams deliberately built in redundancy—multiple developers, testers, and designers overlapping. Vibe coding trades away that safety net.
    3. The Cost vs. Time Tradeoff
      Traditional agile methods are slower and more expensive, but they distribute responsibility and catch issues early. Vibe coding saves time and payroll up front, but hidden flaws or rushed design decisions can result in costly rework later. What looks like savings today can become technical debt tomorrow.
    4. Cultural Backlash
      Just as professionals in other domains experience the grief cycle of job dissolutionAgile Symbiosis 6 x 9 v75 (2)The Human Side of Job Transform…, engineers and designers may resist vibe coding. For those steeped in the craft of their work, it can feel dismissive to let AI “auto-generate” what once took years of mastery. Without empathy and deliberate role redesign, organizations risk splitting into “orchestrators” who adapt quickly and “legacy professionals” who feel left behind.

    When Vibe Coding Fits—and When It Doesn’t

    Best Suited For:

    • Early-stage startups chasing speed to market.
    • Proof-of-concept or MVP builds where failure is affordable.
    • Cross-functional teams with broad, complementary skill sets.

    Risky For:

    • Heavily regulated industries (finance, healthcare, government).
    • Mid-to-large companies with legacy structures and compliance requirements.
    • Products requiring global scale, high reliability, or mission-critical security.

    The decision is less about whether vibe coding is “good” or “bad” and more about whether it aligns with the type of problem, company maturity, and risk tolerance at hand.

    A Balanced Path Forward

    Vibe coding should not be mistaken for a replacement of agile—it is an experimental branch of it. Traditional agile practices evolved to mitigate risk: structured ceremonies, testing pipelines, peer reviews. Vibe coding, by contrast, pushes for raw speed and minimal friction.

    The future is not a choice between the two, but a synthesis. Successful leaders will know when to unleash the speed of vibe coding—early ideation, market testing, low-stakes prototypes—and when to rely on agile’s guardrails for scalability, quality, and trust.

    The danger lies in going all-in on either extreme. Organizations locked into rigid agile ceremonies risk losing competitive ground, while those relying exclusively on vibe coding expose themselves to compounding quality and security failures. The opportunity lies in architecting a hybrid model that treats AI as a collaborator, not a shortcut.

    Closing Thoughts

    The potential of vibe coding is real and measurable: small, well-configured teams delivering outcomes that once required far larger headcount. But its risks are real: fragility, hidden flaws, and cultural resistance. To harness its potential responsibly, leaders must approach vibe coding with both optimism and caution—celebrating its speed while putting in place the safeguards that prevent brittleness.

    This perspective is drawn from concepts in my forthcoming book, Agile Symbiosis: The Rise of the Poly-Shaped Professional in the Era of AI, where I explore how small, AI-augmented teams can thrive when human ingenuity and machine execution are deliberately balanced.

Privacy Policy - Terms and Conditions