{
  "schemaVersion": "1.0.0",
  "site": "https://atanasseri.com",
  "source": "prerendered-public-page-snapshot",
  "sitemapSha256": "c8fd7a0617aa14aa5e3073bf40426cb7ded17a6229bbb03eb9310618a9c1bf3a",
  "pages": [
    {
      "url": "https://atanasseri.com/",
      "route": "/",
      "lastModified": "2026-08-21",
      "title": "I Build at the Edge of Uncertainty",
      "description": "Product Manager working across FinTech, consumer credit, financial infrastructure, risk, and AI-native product development.",
      "markdownUrl": "https://atanasseri.com/content/pages/index.md",
      "headings": [
        {
          "level": 1,
          "text": "I Build at the Edge of Uncertainty"
        },
        {
          "level": 2,
          "text": "Turning complexity, risk, and scattered signals into clear product direction, connected systems, and accountable outcomes."
        },
        {
          "level": 2,
          "text": "Agentic Engineering Assurance System"
        }
      ],
      "links": [
        {
          "text": "Read My Story",
          "url": "https://atanasseri.com/about"
        },
        {
          "text": "Explore My Work",
          "url": "https://atanasseri.com/projects"
        },
        {
          "text": "Follow My Journey",
          "url": "https://atanasseri.com/journey"
        },
        {
          "text": "Explore AEAS",
          "url": "https://aeas.atanasseri.com/"
        }
      ],
      "markdown": "Source: https://atanasseri.com/\nLast modified: 2026-08-21\n\nSystems thinking connects financial risk management, FinTech, and AI.\n\n# I Build at the Edge of Uncertainty\n\n## Turning complexity, risk, and scattered signals into clear product direction, connected systems, and accountable outcomes.\n\nI’m Ata Nasseri. My work spans financial markets, regulated infrastructure, consumer credit, venture building, and AI-native products. These are not separate stories. They are different forms of the same work: understanding complex systems, making risk visible, and building a clear path when the map is incomplete.\n\n[Read My Story](https://atanasseri.com/about)\n\n[Explore My Work](https://atanasseri.com/projects)[Follow My Journey](https://atanasseri.com/journey)\n\nFEATURED SYSTEM\n\n## Agentic Engineering Assurance System\n\nA governed framework for making AI-assisted engineering more reviewable, auditable, and accountable.\n\n[Explore AEAS](https://aeas.atanasseri.com/)\n\n“I do my best work when the problem matters, the path is unclear, and shallow answers are not enough.”\n",
      "contentSha256": "d86cad2bad95b925440db0c6f736b115095aba4fd27820a9eea31721d187fc77"
    },
    {
      "url": "https://atanasseri.com/about",
      "route": "/about",
      "lastModified": "2026-08-21",
      "title": "About Ata Nasseri",
      "description": "Explore Ata Nasseri's path across journalism, financial markets, regulated infrastructure, consumer credit, venture building, and AI-native products.",
      "markdownUrl": "https://atanasseri.com/content/pages/about.md",
      "headings": [
        {
          "level": 1,
          "text": "About Ata Nasseri"
        },
        {
          "level": 2,
          "text": "My Story: Learning to Build Without a Complete Map"
        },
        {
          "level": 2,
          "text": "How I Work"
        },
        {
          "level": 3,
          "text": "Make Assumptions Visible"
        },
        {
          "level": 3,
          "text": "Own the Problem End to End"
        },
        {
          "level": 3,
          "text": "Move with Risk in View"
        },
        {
          "level": 3,
          "text": "Keep Judgment Human"
        },
        {
          "level": 2,
          "text": "What Connects My Dots?"
        },
        {
          "level": 2,
          "text": "Where I Create Value"
        },
        {
          "level": 3,
          "text": "Financial Infrastructure & Risk"
        },
        {
          "level": 3,
          "text": "Consumer Credit & Product Ownership"
        },
        {
          "level": 3,
          "text": "AI-Native Products & Venture Building"
        },
        {
          "level": 2,
          "text": "The Line That Learned to Build"
        },
        {
          "level": 3,
          "text": "Listening for Signal"
        },
        {
          "level": 3,
          "text": "Building Market Judgment"
        },
        {
          "level": 3,
          "text": "Building Trust into Infrastructure"
        },
        {
          "level": 3,
          "text": "Turning Risk into Product"
        },
        {
          "level": 3,
          "text": "Building with AI, Keeping Judgment Human"
        }
      ],
      "links": [
        {
          "text": "View the Full CV",
          "url": "https://atanasseri.com/cv"
        }
      ],
      "markdown": "Source: https://atanasseri.com/about\nLast modified: 2026-08-21\n\n# About Ata Nasseri\n\nProfessional portrait of Ata Nasseri\n\nA product manager, systems thinker, and builder working where finance, risk, technology, and human judgment meet. I turn ambiguous problems into clear product direction, executable systems, and accountable outcomes.\n\n## My Story: Learning to Build Without a Complete Map\n\nMy career did not follow a straight line. It moved through journalism, education, entrepreneurship, financial markets, regulated infrastructure, consumer credit, risk, and AI-native product development. From the outside, these may look like separate worlds. To me, they are different ways of learning how complex systems behave.\n\nJournalism taught me to listen before reaching conclusions, find the signal inside noise, and make difficult ideas understandable. Venture building taught me that an idea creates value only when it can survive contact with users, constraints, operations, and reality.\n\nWorking in financial markets and regulated infrastructure showed me that trust is not an abstract principle. It must be designed into records, rules, controls, decision rights, and the architecture of the system itself.\n\nConsumer credit made product ownership tangible from beginning to end. The product was not only an approval decision. It connected customer needs, affordability, pricing, contracts, funding, construction milestones, repayment behavior, exceptions, and recovery. Every local decision affected the wider system.\n\nToday, in H2Learn and my AI-native product work, I continue to work with incomplete maps. I use AI to explore more deeply and build faster, while keeping evidence, judgment, and accountability human.\n\nThe common thread is not a particular industry. It is the kind of problem I choose to own: consequential problems with connected risks, incomplete information, and no obvious path forward.\n\n## How I Work\n\n### Make Assumptions Visible\n\nAmbiguity becomes manageable when hidden assumptions, constraints, dependencies, and unanswered questions are brought into view.\n\n### Own the Problem End to End\n\nProduct ownership means staying accountable across discovery, decisions, execution, operations, exceptions, and outcomes, not only managing a backlog.\n\n### Move with Risk in View\n\nProgress does not require perfect certainty. It requires understanding what can fail, what matters most, and which decisions remain reversible.\n\n### Keep Judgment Human\n\nAI can expand the field of view and accelerate exploration. Evidence, accountability, and consequential decisions must remain human.\n\n[View the Full CV](https://atanasseri.com/cv)\n\n## What Connects My Dots?\n\nAcross journalism, venture building, financial infrastructure, consumer credit, risk, and AI-native product development, the same pattern keeps returning.\n\nI enter when the information is incomplete and the problem crosses organizational boundaries. I make assumptions visible, identify the decisions that matter, and connect elements that are often managed separately: customer and economics, growth and risk, policy and operations, strategy and execution, human judgment and intelligent systems.\n\nThe dots matter, but value comes from understanding the relationships between them. That is how scattered signals become a product direction, and how direction becomes an executable system.\n\n## Where I Create Value\n\n### Financial Infrastructure & Risk\n\nDesigning and improving systems in which records, controls, regulation, operational reliability, and trust must work together.\n\n### Consumer Credit & Product Ownership\n\nConnecting customer journeys, credit decisions, economics, operations, servicing, exceptions, and recovery into one accountable product system.\n\n### AI-Native Products & Venture Building\n\nUsing AI to explore, prototype, and operate with greater leverage while keeping evidence, product judgment, and responsibility human.\n\n## The Line That Learned to Build\n\n- Journalism & Market Analysis\n\n### Listening for Signal\n\nJournalism taught me to observe before concluding, understand different audiences, find meaningful signals inside noise, and translate complexity into language people can act on.\n\n- Investment, Venture Building & Financial Markets\n\n### Building Market Judgment\n\nEntrepreneurship, investment analysis, and financial markets taught me to move without perfect information, test assumptions against reality, and understand how value, incentives, and risk interact.\n\n- FundReg, CCP, Post-Trade & Regulatory Systems\n\n### Building Trust into Infrastructure\n\nWorking with regulated financial infrastructure showed me that trust must be engineered into data, rules, controls, validation, governance, and the operating model, not added later as a promise.\n\n- Consumer Credit, Market Risk & Operational Workflows\n\n### Turning Risk into Product\n\nCredit and risk work taught me to connect policies, customer journeys, pricing, contracts, operational handoffs, monitoring, exceptions, and outcomes into one end-to-end product.\n\n- H2Learn, Airsheet, Gader & Solofounders\n\n### Building with AI, Keeping Judgment Human\n\nMy current work uses AI to explore more deeply, prototype faster, and operate with more leverage, while ensuring that evidence, consequential decisions, and accountability remain human.\n",
      "contentSha256": "74fa999aa7eadf781c0e856d697abd980f127198da066f8e11befae4818de450"
    },
    {
      "url": "https://atanasseri.com/journey",
      "route": "/journey",
      "lastModified": "2026-08-21",
      "title": "My Journey: How the Line Learned to Build",
      "description": "Five lessons from journalism, financial infrastructure, consumer credit, product discovery, and human-centered AI product development.",
      "markdownUrl": "https://atanasseri.com/content/pages/journey.md",
      "headings": [
        {
          "level": 1,
          "text": "My Journey: How the Line Learned to Build"
        },
        {
          "level": 2,
          "text": "Listening for Signal: What Journalism Taught Me About Product"
        },
        {
          "level": 3,
          "text": "Key Insights:"
        },
        {
          "level": 2,
          "text": "Trust Is an Architecture, Not a Promise"
        },
        {
          "level": 3,
          "text": "Key Insights:"
        },
        {
          "level": 2,
          "text": "Turning Risk into a Product People Can Move Through"
        },
        {
          "level": 3,
          "text": "Key Insights:"
        },
        {
          "level": 2,
          "text": "When Evidence Redraws the Map"
        },
        {
          "level": 3,
          "text": "Key Insights:"
        },
        {
          "level": 2,
          "text": "Building with AI, Keeping Judgment Human"
        },
        {
          "level": 3,
          "text": "Key Insights:"
        }
      ],
      "links": [
        {
          "text": "Start a Conversation",
          "url": "https://atanasseri.com/contact"
        }
      ],
      "markdown": "Source: https://atanasseri.com/journey\nLast modified: 2026-08-21\n\n# My Journey: How the Line Learned to Build\n\nThis is not a chronological list of roles. It is a record of how my way of seeing problems evolved: how listening became judgment, judgment became structure, structure became product ownership, and product ownership expanded into AI-native building. Each chapter changed the way I work. Together, they explain why I am most useful when the problem matters, the path is unclear, and the system cannot be understood from only one perspective.\n\n## Listening for Signal: What Journalism Taught Me About Product\n\nStorytellingSignal DetectionAudience UnderstandingComplexity\n\nJournalism taught me that the first version of a problem is rarely the complete one. Before writing, I had to listen, compare perspectives, test what appeared important, and understand what an audience actually needed to know. That discipline still shapes my product work. Good discovery is not collecting more information. It is distinguishing signal from noise and turning complexity into something people can understand and act on.\n\n### Key Insights:\n\n- Listen before defining the problem.\n\n- Separate what is visible from what is consequential.\n\n- Make complexity understandable without making it shallow.\n\nVisual representation of separating signal from noise\n\nVisual representation of separating signal from noise\n\n## Trust Is an Architecture, Not a Promise\n\nFinTechFinancial InfrastructureRegulationSystem Design\n\nWork in post-trade and financial-market infrastructure showed me that trust depends on the design of the system: how records are structured, how ownership is validated, how exceptions are handled, and how decision rights are distributed. Invisible infrastructure carries visible consequences. When records, regulation, operations, and technology do not align, risk travels across the entire system.\n\n### Key Insights:\n\n- Trust must be built into the operating model.\n\n- Fragmented information creates operational and systemic risk.\n\n- Regulation, product, data, and implementation cannot be designed separately.\n\nArchitecture and system design visualization\n\nArchitecture and system design visualization\n\n## Turning Risk into a Product People Can Move Through\n\nConsumer CreditProduct OwnershipRiskOperations\n\nConsumer credit made the meaning of end-to-end ownership concrete. The product connected customer onboarding, affordability, underwriting, pricing, contracts, funding, construction milestones, repayment behavior, servicing, exceptions, and recovery. The work was not about removing risk. It was about making risk visible, turning policy into executable decisions, and creating a path that customers and internal teams could actually move through.\n\n### Key Insights:\n\n- A credit product is a connected lifecycle, not a single approval.\n\n- Local decisions create system-wide consequences.\n\n- Speed and risk control can improve together when the operating model is redesigned.\n\nConsumer credit and risk path visualization\n\nConsumer credit and risk path visualization\n\n## When Evidence Redraws the Map\n\nH2LearnProduct DiscoveryPivotStakeholder Alignment\n\nH2Learn began with a broad ecosystem challenge and multiple possible product directions. I translated that ambiguity into product logic, user journeys, data structures, and a working prototype. As stakeholder evidence became clearer, the most valuable direction changed. The product moved toward a simpler, initiative-centered map. The pivot was not a retreat from the original work; it was the result of learning what the system actually needed.\n\n### Key Insights:\n\n- A strong product direction must remain challengeable.\n\n- Prototypes are instruments for learning, not proof that the first idea was correct.\n\n- Simplification is valuable when it follows evidence.\n\nProduct discovery and map redrawing\n\nProduct discovery and map redrawing\n\n## Building with AI, Keeping Judgment Human\n\nAI-Native ProductHuman-in-the-LoopVenture BuildingAccountability\n\nAI is now part of how I investigate, design, prototype, and operate. It allows me to explore alternatives more deeply, connect more information, and move from ambiguity to a working model faster. But leverage is not the same as authority. AI can widen the field of view; it cannot own the consequences of the direction chosen. My work in H2Learn, Airsheet, Gader, and Solofounders is shaped by that boundary.\n\n### Key Insights:\n\n- Use AI to increase the depth and speed of exploration.\n\n- Keep evidence and consequential decisions reviewable.\n\n- Design intelligent products around human responsibility.\n\nAI integration with human judgment\n\nAI integration with human judgment\n\nWorking on a problem where the map is incomplete?\n\n[Start a Conversation](https://atanasseri.com/contact)\n",
      "contentSha256": "b98cb3e4740fe639713e55765c3bc020f48d1ca827b4464436df941c2fe9cede"
    },
    {
      "url": "https://atanasseri.com/projects",
      "route": "/projects",
      "lastModified": "2026-09-08",
      "title": "Proof of Work: From Uncertainty to Outcomes",
      "description": "Selected product work across product discovery, AI-native operations, venture building, financial infrastructure, and complex system design.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects.md",
      "headings": [
        {
          "level": 1,
          "text": "Proof of Work: From Uncertainty to Outcomes"
        },
        {
          "level": 2,
          "text": "Agentic Development Orchestrator"
        },
        {
          "level": 2,
          "text": "H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product"
        },
        {
          "level": 2,
          "text": "Consumer Credit: Turning a Fragmented Process into One Product System"
        },
        {
          "level": 2,
          "text": "FundReg: Building Trust into Financial-Market Infrastructure"
        },
        {
          "level": 2,
          "text": "Airsheet: From Generic No-Code to AI-Native Nonprofit Operations"
        },
        {
          "level": 2,
          "text": "Gader: Designing Technology That Moves into the Background"
        }
      ],
      "links": [
        {
          "text": "Read this project: Agentic Development Orchestrator",
          "url": "https://atanasseri.com/projects/agentic-development-orchestrator"
        },
        {
          "text": "Read this project: H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product",
          "url": "https://atanasseri.com/projects/h2learn"
        },
        {
          "text": "Read this project: Consumer Credit: Turning a Fragmented Process into One Product System",
          "url": "https://atanasseri.com/projects/consumer-credit"
        },
        {
          "text": "Read this project: FundReg: Building Trust into Financial-Market Infrastructure",
          "url": "https://atanasseri.com/projects/fundreg"
        },
        {
          "text": "Read this project: Airsheet: From Generic No-Code to AI-Native Nonprofit Operations",
          "url": "https://atanasseri.com/projects/airsheet"
        },
        {
          "text": "Read this project: Gader: Designing Technology That Moves into the Background",
          "url": "https://atanasseri.com/projects/gader"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects\nLast modified: 2026-09-08\n\n# Proof of Work: From Uncertainty to Outcomes\n\nSelected work showing how I frame ambiguous problems, connect product and risk, and turn direction into systems people can use.\n\n## Agentic Development Orchestrator\n\nAI EngineeringSystems DesignGovernance\n\nAgentic Development Orchestrator: implementation, read-only audit, and an explicit owner decision loop\n\nAn interactive evidence-led case study of a governed coding workflow that connects implementation, separate read-only audit, remediation, authority, and traceable evidence.\n\nStable evidence snapshot: 31 August 2026\n\n[Read this project: Agentic Development Orchestrator](https://atanasseri.com/projects/agentic-development-orchestrator)\n\n## H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product\n\nProduct ManagementSolution ArchitectureEcosystem DiscoveryHuman-in-the-LoopAI-Native Product\n\nH2Learn ecosystem map and prototype visualization\n\nA stakeholder-reviewed product prototype for discovering initiatives, organizations, and collaboration opportunities across the hydrogen learning ecosystem.\n\nMy role: Product Manager\n\n[Read this project: H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product](https://atanasseri.com/projects/h2learn)\n\n## Consumer Credit: Turning a Fragmented Process into One Product System\n\nConsumer CreditEnd-to-End Product OwnershipCredit RiskOperationsProperty-Secured Finance\n\nVisualization of consumer credit lifecycle\n\nAn end-to-end consumer-credit lifecycle embedded in off-plan residential purchases.\n\nMy role: Product Manager\n\nMaskan Investment Group (MIG)\n\n[Read this project: Consumer Credit: Turning a Fragmented Process into One Product System](https://atanasseri.com/projects/consumer-credit)\n\n## FundReg: Building Trust into Financial-Market Infrastructure\n\nFinancial InfrastructureMutual FundsPost-TradeRegulatory SystemsProduct Management\n\nVisualization of FundReg infrastructure\n\nA centralized national mutual-fund ownership registry designed for integrity, oversight, and investor protection.\n\nMy role: Product Manager for Post-Trade & Mutual Fund Registry Infrastructure\n\nCentral Securities Depository of Iran (CSDI)\n\n[Read this project: FundReg: Building Trust into Financial-Market Infrastructure](https://atanasseri.com/projects/fundreg)\n\n## Airsheet: From Generic No-Code to AI-Native Nonprofit Operations\n\nAI-Native ProductNonprofit OperationsProduct DiscoveryVenture BuildingHuman Review\n\nAirsheet AI-native operations visual\n\nA focused AI-native operations product hypothesis for nonprofit teams.\n\nMy role: Founder & Product Lead\n\nSolofounders\n\n[Read this project: Airsheet: From Generic No-Code to AI-Native Nonprofit Operations](https://atanasseri.com/projects/airsheet)\n\n## Gader: Designing Technology That Moves into the Background\n\nLocal-First ProductSocial DiscoveryPWAAndroidAI-Native Product\n\nGader local-first social product visual\n\nA local-first social product centered on nearby activities and real human connection.\n\nMy role: Founder & Product Lead\n\nSolofounders\n\n[Read this project: Gader: Designing Technology That Moves into the Background](https://atanasseri.com/projects/gader)\n",
      "contentSha256": "52303998d7fc53196d05f308216deee0ee4add6339a970c0a3b55646144ef9cd"
    },
    {
      "url": "https://atanasseri.com/projects/agentic-development-orchestrator",
      "route": "/projects/agentic-development-orchestrator",
      "lastModified": "2026-09-02",
      "title": "A coding system that can challenge its own work.",
      "description": "An interactive evidence-led case study of a governed coding workflow that connects implementation, separate read-only audit, remediation, authority, and traceable evidence.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/agentic-development-orchestrator.md",
      "headings": [
        {
          "level": 1,
          "text": "A coding system that can challenge its own work."
        },
        {
          "level": 2,
          "text": "Human authority stays. Unnecessary interruption goes."
        },
        {
          "level": 2,
          "text": "One change becomes a traceable loop."
        },
        {
          "level": 2,
          "text": "The attested audit surface grew from 81 to 329 paths."
        },
        {
          "level": 2,
          "text": "The second round challenged the first again."
        },
        {
          "level": 2,
          "text": "118 findings stayed visible, by severity and round."
        },
        {
          "level": 2,
          "text": "Audit time was measured, not guessed."
        },
        {
          "level": 2,
          "text": "A recorded disposition is not a verified outcome."
        },
        {
          "level": 2,
          "text": "Automation must prove its right to continue."
        },
        {
          "level": 3,
          "text": "Unresolved CRITICAL or HIGH finding"
        },
        {
          "level": 3,
          "text": "Package-caused validation regression"
        },
        {
          "level": 3,
          "text": "Material scope or architecture change"
        },
        {
          "level": 3,
          "text": "Material residual risk"
        },
        {
          "level": 3,
          "text": "New credential, destructive action, or authority requirement"
        },
        {
          "level": 3,
          "text": "Remediation not proven through execution"
        },
        {
          "level": 3,
          "text": "ResultScenario: All evidence clear"
        },
        {
          "level": 2,
          "text": "Evidence is part of the product."
        },
        {
          "level": 2,
          "text": "The foundation is operational. The larger vision is still being built."
        },
        {
          "level": 3,
          "text": "Operational in stable evidence"
        },
        {
          "level": 3,
          "text": "In implementation outside the stable snapshot"
        },
        {
          "level": 3,
          "text": "Future direction"
        },
        {
          "level": 3,
          "text": "Retained fallback"
        },
        {
          "level": 2,
          "text": "How to read these numbers"
        }
      ],
      "links": [
        {
          "text": "Explore the system",
          "url": "https://atanasseri.com/projects/agentic-development-orchestrator#authority"
        },
        {
          "text": "Inspect the evidence",
          "url": "https://atanasseri.com/projects/agentic-development-orchestrator#surface"
        },
        {
          "text": "Read the methodology",
          "url": "https://atanasseri.com/projects/agentic-development-orchestrator#methodology"
        },
        {
          "text": "Show in evidence graph · Manual fallback",
          "url": "https://atanasseri.com/projects/agentic-development-orchestrator#evidence"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/agentic-development-orchestrator\nLast modified: 2026-09-02\n\nAGENTIC DEVELOPMENT ORCHESTRATOR\n\n# A coding system that can challenge its own work.\n\nAgentic Development Orchestrator is a governed engineering loop that binds implementation, a separate read-only audit role, evidence, remediation, and approval to exact review snapshots. It aims to remove unnecessary workflow interruption while keeping human authority, stop conditions, rollback, and evidence explicit.\n\nStable evidence snapshot: 31 August 2026\n\n[Explore the system](https://atanasseri.com/projects/agentic-development-orchestrator#authority)[Inspect the evidence](https://atanasseri.com/projects/agentic-development-orchestrator#surface)\n\n- ReviewsTen distinct Review packages in the stable snapshot\n\n-\n\n-\n\n-\n\nRepository-derived values from one stable snapshot. These figures are evidence history, not a quality score.\n\nThe governed loop\n\nEight named states from owner mandate through implementation, pinned review, read-only audit, remediation, decision, evidence, and promotion or stop, with a mandatory verification round, a dashed owner-escalation branch, a stop branch with manual fallback retained, and dotted record links into the evidence node. Each node is a button: hover, focus, or tap for its role, trigger, input, action, output, authority basis, prohibited actions, failure behavior, and current status.\n\n- Operational in stable evidence\n\n- Operational foundation; automatic approval in implementation · dashed ring\n\n- Future direction · not in this loop\n\n- Authority\n\n- Engineering\n\n- Assurance\n\n- Evidence\n\nRead-only audit · Separate read-only audit roleCurrent selection\n\nTrigger\n\nA pinned review snapshot is presented.\n\nInput\n\nThe exact pinned review snapshot.\n\nAction\n\nInspects the snapshot, runs read-only analysis, reports findings, and issues a verdict.\n\nOutput\n\nAudit report and verdict.\n\nAuthority basis\n\nA separate system role. It is not a third-party certification or independent assurance firm.\n\nProhibited\n\nCannot implement, widen scope, approve, or authorize continuation.\n\nFailure behavior\n\nStops on unverifiable identity or evidence and records NOT\\_AUDITABLE rather than a clean result.\n\nLoop state\n\nAuditing\n\nOperational in stable evidence\n\nReviews the exact pinned snapshot and produces a report and verdict. It cannot implement, widen scope, authorize continuation, or silently convert unknown evidence into approval.\n\nThe diagram is an explanatory model of the governed workflow. Current implementation status is shown separately and must not be inferred from animation alone. Stable evidence snapshot: 31 August 2026.\n\n01 · AUTHORITY\n\n## Human authority stays. Unnecessary interruption goes.\n\nThe system is not designed to replace the owner. It separates authority from execution so that routine, already-authorized work can continue without repeatedly asking the owner to restate the same decision.\n\nThe owner defines the mission, scope, risk boundary, and permissions. The implementation role changes the system. The audit role challenges a pinned snapshot. Evidence records what happened. When authority or evidence is insufficient, the loop stops or escalates.\n\nAutomation may execute within authority. It may not invent authority.\n\n-\n\n-\n\n-\n\n-\n\nMethod. These lanes describe responsibilities and decision boundaries. They do not claim hard operating-system privilege isolation between every role.\n\nAuthority map\n\n5 roles · 7 artifacts · 27 links\n\nFour responsibility lanes: Authority, Engineering, Assurance, and Evidence, with role nodes, artifact nodes, production and consumption links, owner-only decision points, and a stop or escalation boundary toward the owner. The role-to-action matrix and the artifact matrix below list the same mapping.\n\n- Produces (role → artifact)\n\n- Consumes (artifact → role)\n\n- Owner-only decision point\n\n- Stop or escalation boundary\n\n- Automatic path in implementation (hatched)\n\n- Explanatory artifact class (dotted outline)\n\nMission mandate · Authority lane · artifactCurrent selection\n\nArtifact\n\nMission mandate\n\nQuestion answered\n\nWhat was authorized, by whom, and within which boundary?\n\nProduced by\n\nOwner\n\nConsumed by\n\nImplementation role · Resident orchestrator\n\nIntegrity meaning\n\nDefines the permitted mission, scope, authority, expiry, and stop boundary.\n\nDepends on\n\nOwner authority\n\nNext allowed state\n\nauthorizes Work package and change scope; provides the authority boundary to Approval provenance\n\nStop condition\n\nOwner-only decision point. Automation stops at the boundary; the owner decides.\n\nImplementation status\n\nExplanatory artifact class\n\nBasis: Interpreted · explanatory artifact model from the stable snapshot stable-2026-08-31. Status labels: Current status as of 31 August 2026.\n\n02 · THE LOOP\n\n## One change becomes a traceable loop.\n\nA change is not treated as complete when code exists. It moves through an implementation handoff, a pinned review snapshot, a separate audit, a recorded response, a mandatory verification round, and an explicit approval or escalation path.\n\nEvery consequential transition should leave a durable artifact. The system is designed so that a later reviewer can ask what was authorized, which exact tree was examined, what was found, what changed, and why continuation was permitted.\n\nThe product is not only the code. The product is also the trace that explains why the code was allowed to move.\n\nRoute\n\nWorkflow outcomes\n\n- Continue within authority\n\n- Remediate and verify\n\n- Escalate to owner\n\n- Stop on unverifiable state\n\n- Retain manual fallback\n\n- Active route\n\n- Other branches\n\n- Durable output\n\n- Operational foundation; automatic approval in implementation\n\n- Retained fallback\n\nThe diagram is an explanatory model of the governed workflow. Current implementation status is shown separately and must not be inferred from animation alone.\n\nGoverned workflow explorer\n\nRoute: Normal governed completion · 12 of 13 stages\n\nThirteen workflow stages from mission and work package to promotion, escalation, or manual fallback, laid out as a serpentine with every branch visible. The Normal governed completion route is emphasised. Each stage shows its durable output; implementation status is a separate field.\n\n05 · Read-only audit · Separate read-only audit roleCurrent selection\n\nOperational in stable evidence\n\nReviews the exact pinned snapshot and produces a report and verdict. It cannot implement, widen scope, authorize continuation, or silently convert unknown evidence into approval.\n\nRoute\n\nNormal governed completion\n\nTrigger\n\nAudit directive for a pinned snapshot.\n\nInput\n\nThe exact pinned review snapshot.\n\nAction\n\nInspects the snapshot with read-only analysis and reports findings.\n\nDurable output\n\nAudit report draft.\n\nState before\n\nAudit requested.\n\nState after\n\nAuditing.\n\nStop condition\n\nUnverifiable identity or evidence; the report records NOT\\_AUDITABLE.\n\nNext on this route\n\n06 · Committed report and evidence witness\n\nBasis: Current status · As of 31 August 2026\n\nExplanatory model, not a live run. Stable evidence snapshot: 31 August 2026.\n\n03 · AUDITED SURFACE\n\n## The attested audit surface grew from 81 to 329 paths.\n\nThe first measurable audit report recorded 81 attested paths. The latest report in the stable snapshot recorded 329. Across the sequence, the audit surface expanded as the system accumulated workflow controls, evidence handling, recovery logic, orchestration, and governance.\n\n4.06× larger attested surface\n\n- First measurable report81\n\n- Latest report329\n\n- Canonical reports21\n\n- Stable repository files299\n\nReport in view\n\n- ReportR10.2 · Review 10\n\n- Date30 Aug 2026\n\n- Attested paths329\n\n- Findings8 · 4 HIGH · 4 MEDIUM\n\n- Recorded duration17m 45s\n\n- VerdictChanges required\n\nRound\n\n- Round 1\n\n- Round 2\n\n- Historical Round 3\n\n- Historical Round 3 · dashed link off the series\n\n- Not recorded · NOT\\_AUDITABLE\n\nRecorded attested path count by audit report\n\nAll 21 reports\n\nOrdered sequence of 21 audit reports on the horizontal axis with the audit File Count recorded by each report on the vertical axis, from 0 to 350. First measurable File Count 81 at R01.2; latest 329 at R10.2; derived change 4.06×. R01.1 is NOT\\_AUDITABLE with no recorded File Count and is drawn as an explicit missing mark at the baseline, not as zero. Round 1 and Round 2 are filled marks joined by a solid line; the historical Round 3 report is an outlined diamond linked to its neighbours by a dashed path. Mark size scales with the findings total. The stable repository file count of 299 is a different measure and is shown only as a separate note, not on the axis.\n\nUse Left and Right arrow keys to move between reports, Home and End to jump to the first and last report, Enter or Space to pin a report, and Escape to clear the pin.\n\nR10.2 · Review 10 · Canonical audit report in the stable evidence snapshotCurrent selection\n\nDate\n\n30 Aug 2026\n\nRound\n\nRound 2\n\nFile Count\n\n329\n\nFindings\n\n8\n\nHIGH · MEDIUM\n\n4 · 4\n\nRecorded duration\n\n17m 45s\n\nVerdict\n\nChanges required\n\nRecorded disposition\n\n8 fixed · 0 accepted risk · 0 owner decision\n\nLatest report in the stable snapshot.\n\nCaveat. Audit File Count is the number of attested paths recorded by the report. Repository file count is the number of blobs in the stable Git tree. They are related measures, but they are not interchangeable and must not share one axis as if they were identical. A larger audit surface means more material was presented for review. It does not, by itself, prove greater security, quality, or completeness. Mark area scales with each report's findings total; the NOT\\_AUDITABLE record is drawn as an open mark at the baseline, not as zero. Basis: Reported File Count, findings, and verdict; Derived multiple (329 ÷ 81 = 4.06×) and formatted duration; Historical exception for R01.1 and R01.3. Stable evidence snapshot: 31 August 2026.\n\n04 · TWO ROUNDS\n\n## The second round challenged the first again.\n\nFor Reviews 02 through 10, Round 1 recorded 62 findings and Round 2 recorded 52. Most review pairs stayed level or declined, but one review increased from 8 findings to 12.\n\nThe second round is not a ceremonial sign-off. It can expose new defects, incomplete remediation, regressions, and adjacent risks.\n\nMeasure\n\nCurrent values\n\n- ReviewAll nine paired reviews\n\n- MeasurePaired findings\n\n- Round 162\n\n- Round 252\n\n- Difference−10\n\n- Directiondecreased\n\nHighlighted exception: Review 04 increased from 8 findings in Round 1 to 12 in Round 2.\n\nAggregate · Round 1 → Round 2\n\n- Paired findings62 → 52\n\n- HIGH32 → 24\n\n- MEDIUM30 → 28\n\nThe difference between rounds is descriptive. It is not a controlled measure of code quality, remediation effectiveness, or audit difficulty.\n\nRound 1 and Round 2 recorded findings, Review 02 to Review 10\n\nPaired findings · Round 1 → Round 2 · 9 paired reviews\n\nFor Reviews 02 through 10, Round 1 recorded 62 findings and Round 2 recorded 52. Most review pairs stayed level or declined, but one review increased from 8 findings to 12. Review 04 increased from 8 findings in Round 1 to 12 in Round 2. The chart is a slopegraph: two columns show each review's Round 1 value on the left and Round 2 value on the right, joined by a straight line. A falling line marks a decrease, a rising line an increase, and a level line no change. Review 04 is drawn heavier and annotated. The aggregate for all nine paired reviews is drawn separately above the reviews on its own scale.\n\n- Round 1\n\n- Round 2\n\n- Highlighted exception\n\nAll nine paired reviews · Paired findingsCurrent selection\n\nRound 1\n\n62\n\nRound 2\n\n52\n\nAbsolute difference\n\n−10\n\nDirection\n\ndecreased\n\nBasis: Reported counts per report; differences derived. Stable evidence snapshot: 31 August 2026.\n\n05 · AUDIT ATLAS\n\n## 118 findings stayed visible, by severity and round.\n\nThe stable evidence history contains 56 HIGH and 62 MEDIUM findings across 21 reports. No finding was recorded as CRITICAL in this snapshot.\n\n- Reports21\n\n- Recorded findings118\n\n- CRITICAL0\n\n- HIGH56\n\n- MEDIUM62\n\nFinding count measures what the audits recorded. It is not a defect density, risk score, or comparison with another project.\n\nSelect a review, round, or severity to see the same evidence reorganized without losing the total context.\n\nRound\n\nSeverity\n\nVisible subset\n\nVisible 118 of 118 recorded findings · Stable total 118 across 21 reports ·\n\nR01.1 · Identity or evidence conditions prevented a substantive audit. This is not a clean zero-finding report.\n\nR01.3 · This report belongs to an earlier governance process and does not imply that the current process permits an automatic third round.\n\nRecorded findings by review, round, and severity\n\n56 HIGH · 62 MEDIUM · 0 CRITICAL across 21 reports · 118 recorded findings\n\nRecorded findings by review, round, and severity. Ten review groups on the horizontal axis, one column per audit round inside each group, HIGH recorded findings stacked below MEDIUM. Review 01 Round 1 is marked NOT\\_AUDITABLE rather than drawn as a zero-height column; Review 01 Round 3 is a historical third round drawn hatched. Tab into the chart, use the arrow keys to move between the 21 reports, Enter to pin a report, Escape to clear. 56 HIGH · 62 MEDIUM · 0 CRITICAL across 21 reports · 118 recorded findings.\n\n- HIGH56\n\n- MEDIUM62\n\n- CRITICAL (no finding recorded as CRITICAL)0\n\n- Round 1\n\n- Round 2\n\n- Historical Round 3\n\n- NOT\\_AUDITABLE · historical exception\n\n21 reports · 10 reviews · all rounds · stable snapshot stable-2026-08-31Current selection\n\nRecorded findings\n\n118\n\nHIGH\n\n56\n\nMEDIUM\n\n62\n\nCRITICAL\n\n0\n\nRecorded disposition\n\n113 fixed · 3 accepted risk · 2 owner decision\n\nNo finding was recorded as CRITICAL in this snapshot.\n\nCanonical audit report in the stable evidence snapshot. Severity counts Reported; totals Derived. Stable snapshot stable-2026-08-31, as of 31 August 2026.\n\n06 · MEASURED TIME\n\n## Audit time was measured, not guessed.\n\nThe 21 reports record 17,825 seconds of audit time, equal to 297 minutes and 5 seconds. The median report duration was 14 minutes and 18 seconds.\n\n- Total recorded time297m 05s\n\n- Mean across all reports14m 09s\n\n- Median across all reports14m 18s\n\n- Mean across nonzero reports14m 51s\n\n- Shortest nonzero record1m 01s\n\n- Longest record21m 53s\n\nView\n\nRound\n\n- Round 1\n\n- Round 2\n\n- Historical Round 3\n\n- NOT\\_AUDITABLE · historical exception\n\n- Median 14m 18s\n\nThese timestamps measure the audit-report interval. They do not measure the full engineering cycle, waiting time, remediation time, owner time, or end-to-end delivery time.\n\nHistorical exception. Review 01 Round 1 has identical start and completion timestamps and a NOT\\_AUDITABLE verdict. Its recorded duration is zero and must remain visibly marked as a historical exception.\n\nRecorded audit-report duration by report\n\n21 reports · 17,825 s recorded\n\nLollipop chart of recorded audit-report duration for each of the 21 reports in sequence, with a median reference at 14 minutes and 18 seconds, a zero-duration historical exception for R01.1, and annotations for the longest (R08.2, 21 minutes and 53 seconds) and shortest nonzero (R01.2, 1 minute and 1 second) records.\n\nAll 21 reports · Recorded audit-report duration by reportCurrent selection\n\nTotal recorded time\n\n297m 05s (17,825 s)\n\nMedian\n\n14m 18s\n\nMean\n\n14m 09s\n\nNonzero mean\n\n14m 51s\n\nReports\n\n21 · 20 nonzero\n\nThese timestamps measure the audit-report interval. They do not measure the full engineering cycle, waiting time, remediation time, owner time, or end-to-end delivery time. Basis: Reported; duration formatting Derived. Stable evidence snapshot: 31 August 2026.\n\n07 · DISPOSITION\n\n## A recorded disposition is not a verified outcome.\n\nEvery canonical finding in the stable snapshot has a recorded disposition. Of 118 findings, 113 were recorded as FIXED, 3 as ACCEPTED\\_RISK, and 2 as OWNER\\_DECISION\\_REQUIRED.\n\n- FIXED (recorded)113\n\n- ACCEPTED\\_RISK (recorded)3\n\n- OWNER\\_DECISION\\_REQUIRED (recorded)2\n\nFIXED (recorded)\n\nThe resolution record states that a fix was made.\n\nACCEPTED\\_RISK (recorded)\n\nThe resolution record accepts the remaining risk.\n\nOWNER\\_DECISION\\_REQUIRED (recorded)\n\nThe resolution record identifies a decision that required owner authority.\n\nFIXED means recorded as fixed in a resolution report. It does not mean that every fix was independently re-audited after the final round.\n\nFollow a flow from severity to recorded disposition, then select a destination to see which review rounds contributed to it.\n\nComplete flow · Stable total 118 findings\n\nRecorded finding disposition\n\n118 findings · stable-2026-08-31\n\nFlow from HIGH (56) and MEDIUM (62) severity to recorded dispositions FIXED (recorded) (113), ACCEPTED\\_RISK (recorded) (3), OWNER\\_DECISION\\_REQUIRED (recorded) (2). Marks are sized in proportion to the count of canonical findings; the complete matrix reconciles to 118.\n\nAll recorded findings · 118 findings · 21 reportsCurrent selection\n\nFIXED (recorded)\n\n113\n\nACCEPTED\\_RISK (recorded)\n\n3\n\nOWNER\\_DECISION\\_REQUIRED (recorded)\n\n2\n\nHIGH severity\n\n56 of 118\n\nMEDIUM severity\n\n62 of 118\n\nRecorded disposition is the resolution status written for each canonical finding. FIXED is a recorded disposition, not independently verified closure. Basis: Recorded and derived · Stable evidence snapshot: 31 August 2026.\n\n08 · CONTINUATION GATES\n\n## Automation must prove its right to continue.\n\nThe proposed standing-mandate path evaluates six gates before automatic approval can be available. A blocked gate or an unverifiable gate routes to owner escalation. Unknown evidence never becomes a silent pass.\n\nAll six gates are CLEAR\n\nAutomatic approval may be available within the governing mandate.\n\nAny gate is BLOCKED\n\nStop automatic continuation and escalate to the owner.\n\nAny gate is UNVERIFIED\n\nStop automatic continuation and escalate to the owner.\n\nThe interesting state is not only blocked. It is unverified. The system must distinguish missing evidence from evidence that passed.\n\n- CLEAR\n\n- BLOCKED\n\n- UNVERIFIED\n\nIn implementation · This simulator explains the intended gate logic. In this package, standing-mandate automatic approval is not represented as a stable main capability.\n\nSix-gate continuation simulator\n\nAll evidence clear\n\nExplanatory simulator with six categorical gates that can each be CLEAR, BLOCKED, or UNVERIFIED. Any BLOCKED or UNVERIFIED gate routes to owner escalation. The capability is in implementation outside the stable snapshot and no real approval is performed.\n\nIN IMPLEMENTATION OUTSIDE THE STABLE SNAPSHOT\n\nThis simulator explains the intended gate logic. In this package, standing-mandate automatic approval is not represented as a stable main capability.\n\nExplanatory simulator · no real approval\n\nPreset scenario\n\nResultAutomatic approval may be available within the governing mandate.\n\n- Gate 1, G1\n\n### Unresolved CRITICAL or HIGH finding\n\nDoes the package retain an unresolved CRITICAL or HIGH finding?\n\nControl type\n\nMachine checked\n\nEvidence required\n\nValidated canonical findings and their current recorded disposition.\n\nCLEAR\n\nNo unresolved CRITICAL or HIGH finding remains within the evaluated package.\n\nState · Gate 1\n\n- Gate 2, G2\n\n### Package-caused validation regression\n\nDid the package cause a validation regression?\n\nControl type\n\nMachine checked\n\nEvidence required\n\nComparable validation evidence bound to the evaluated package and baseline.\n\nCLEAR\n\nRequired validation passes and no package-caused regression is detected.\n\nState · Gate 2\n\n- Gate 3, G3\n\n### Material scope or architecture change\n\nDid remediation introduce a material scope or architecture change outside the authorized envelope?\n\nControl type\n\nMixed check and assertion\n\nEvidence required\n\nValidated change boundary plus an explicit assessment of material scope and architecture impact.\n\nCLEAR\n\nThe change remains within the authorized material scope and architecture boundary.\n\nState · Gate 3\n\n- Gate 4, G4\n\n### Material residual risk\n\nDoes material residual risk remain after remediation?\n\nControl type\n\nEvidence-bearing assertion\n\nEvidence required\n\nExplicit residual-risk assessment linked to findings, remediation, validation, and known limitations.\n\nCLEAR\n\nNo material residual risk requiring owner authority remains.\n\nState · Gate 4\n\n- Gate 5, G5\n\n### New credential, destructive action, or authority requirement\n\nDoes continuation require a new credential, destructive action, or authority not already granted?\n\nControl type\n\nEvidence-bearing assertion\n\nEvidence required\n\nExplicit action and authority inventory for the evaluated continuation.\n\nCLEAR\n\nNo new credential, destructive action, or additional authority is required.\n\nState · Gate 5\n\n- Gate 6, G6\n\n### Remediation not proven through execution\n\nHas the relevant remediation been proven through execution?\n\nControl type\n\nEvidence-bearing assertion\n\nEvidence required\n\nExecution evidence linked to the remediation and evaluated package.\n\nCLEAR\n\nRelevant remediation is supported by adequate execution evidence.\n\nState · Gate 6\n\n### ResultScenario: All evidence clear\n\nAutomatic approval may be available within the governing mandate.\n\nExplanatory all-clear scenario. This is not an actual review and no approval is performed.\n\nScenario · All evidence clearCurrent selection\n\nCLEAR\n\n6\n\nBLOCKED\n\n0\n\nUNVERIFIED\n\n0\n\nIn implementation\n\nAutomatic approval may be available within the governing mandate. Explanatory all-clear scenario. This is not an actual review and no approval is performed.\n\nBasis: In implementation · As of 31 August 2026. This dataset powers an explanatory simulator and does not represent a live review. The simulator must not execute commands, mutate a repository, or perform approval.\n\n09 · EVIDENCE\n\n## Evidence is part of the product.\n\nThe system is designed so that authority, implementation, review identity, audit results, remediation, decisions, and promotion can be reconstructed as a connected evidence chain.\n\nSelected artifactDefault\n\nMission mandate · Authority lane\n\nWhat was authorized, by whom, and within which boundary?\n\nProduced by\n\nOwner\n\nConsumed by\n\nImplementation role · Resident orchestrator\n\nIntegrity meaning\n\nDefines the permitted mission, scope, authority, expiry, and stop boundary.\n\nPublic status\n\nExplanatory artifact class\n\nCurrent capability relationship\n\nEvent-driven audit orchestration · Evidence provenance foundation · Standing-mandate automatic approval · Fully autonomous multi-project engineering · Manual fallback and rollback\n\nA claim without provenance is a story. A claim connected to authority, a pinned snapshot, review, and a durable decision becomes inspectable evidence.\n\nThe public graph uses sanitised artifact classes and aliases. It does not expose private commits, paths, account identities, or raw evidence.\n\nEvidence provenance graph\n\n7 artifact classes · 10 relations\n\nSeven sanitised artifact classes laid out in four lanes (Authority, Engineering, Assurance, Evidence) and connected by ten directed relations: authorizes, scopes, is examined by, requires a disposition in, produces the next review candidate for, provides the authority boundary to, provides assurance evidence to, provides response evidence to, permits or escalates to, and closes. Selecting an artifact highlights its direct producers and consumers; a path control extends the highlight from the mission mandate to the promotion and closure record. The tables below list every artifact and relation.\n\n- Authority lane\n\n- Engineering lane\n\n- Assurance lane\n\n- Evidence lane\n\n- Selected artifact\n\n- Direct producer or consumer\n\nMission mandate · Authority lane · What was authorized, by whom, and within which boundary?Current selection\n\nProduced by\n\nOwner\n\nConsumed by\n\nImplementation role · Resident orchestrator\n\nCurrent capability relationship\n\nEvent-driven audit orchestration · Evidence provenance foundation · Standing-mandate automatic approval · Fully autonomous multi-project engineering · Manual fallback and rollback\n\nExplanatory artifact class\n\nDefines the permitted mission, scope, authority, expiry, and stop boundary.\n\nExplanatory artifact-class model from the evidence chain. Stable evidence snapshot: 31 August 2026.\n\n10 · CURRENT STATUS\n\n## The foundation is operational. The larger vision is still being built.\n\nThe stable snapshot contains a working governed audit foundation: pinned review identity, separate read-only audit, recorded findings and resolutions, a two-round challenge model, evidence artifacts, explicit owner decisions, and event-driven orchestration for an explicitly armed project.\n\nStanding-mandate automatic approval is in implementation outside the stable snapshot. Fully autonomous multi-project engineering remains a future direction, not a current public claim. Manual fallback remains part of the design.\n\nThe system does not remove human authority. It removes unnecessary workflow interruption while keeping authority, review, evidence, stop conditions, and rollback explicit.\n\n[Read the methodology](https://atanasseri.com/projects/agentic-development-orchestrator#methodology)\n\nCurrent status · Stable evidence snapshot: 31 August 2026\n\nCapability status ladder\n\nExpanded 9 of 9 capabilities\n\n9 capabilities grouped into 4 status classes, listed in order: operational in stable evidence, in implementation outside the stable snapshot, future direction, retained fallback. Each row states the public status wording, the as-of date, the public claim, the limitation, and the evidence classes that support it.\n\nShow\n\nExpanded 9 of 9 capabilities\n\n- ### Operational in stable evidence\n\n6 capabilities\n\nThe stable snapshot contains implementation and evidence supporting the bounded public claim.\n\n- Pinned and attested review snapshotsOperational in stable evidenceas of 31 August 2026 stable snapshot\n\nThe stable evidence history includes audit reports bound to identified and attested review material.\n\nLimitation Attestation and integrity evidence do not by themselves prove authenticity against every compromised parent or authority source.\n\n- Pinned review snapshot\n\n- Audit report\n\n[Show in evidence graph · Pinned and attested review snapshots](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- Separate read-only Codex audit roleOperational in stable evidenceas of 31 August 2026 stable snapshot\n\nCanonical reports were produced by a separate read-only review role against pinned material.\n\nLimitation This is a separate system role, not a third-party certification or independent assurance firm.\n\n- Pinned review snapshot\n\n- Audit report\n\n[Show in evidence graph · Separate read-only Codex audit role](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- Two-round governed review loopOperational in stable evidenceas of 31 August 2026 stable snapshot\n\nThe stable history contains a governed discovery and verification model for newer reviews.\n\nLimitation Review 01 is a historical exception with an earlier three-round process.\n\n- Audit report\n\n- Resolution record\n\n- Approval provenance\n\n[Show in evidence graph · Two-round governed review loop](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- Findings and resolution traceOperational in stable evidenceas of 31 August 2026 stable snapshot\n\nAll 118 canonical findings in the stable snapshot map to one recorded disposition.\n\nLimitation Recorded FIXED does not mean every fix was independently re-audited after the final round.\n\n- Audit report\n\n- Resolution record\n\n[Show in evidence graph · Findings and resolution trace](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- Event-driven orchestrationOperational for an explicitly armed projectas of 31 August 2026 stable snapshot\n\nThe stable snapshot records event-driven orchestration for an explicitly armed project while material decisions still escalate.\n\nLimitation This does not establish universal multi-project deployment or human-free operation.\n\n- Mission mandate\n\n- Work package and change scope\n\n- Audit report\n\n- Promotion and closure record\n\n[Show in evidence graph · Event-driven orchestration](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- Evidence provenance foundationOperational in stable evidenceas of 31 August 2026 stable snapshot\n\nThe workflow preserves a connected record of scope, review identity, audit, resolution, decision, and closure artifacts.\n\nLimitation The public graph is an artifact-class model and does not claim tamper-proof evidence or cryptographic owner identity.\n\n- Mission mandate\n\n- Work package and change scope\n\n- Pinned review snapshot\n\n- Audit report\n\n- Resolution record\n\n- Approval provenance\n\n- Promotion and closure record\n\n[Show in evidence graph · Evidence provenance foundation](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- ### In implementation outside the stable snapshot\n\n1 capability\n\nWork exists outside the stable public evidence boundary and must not be presented as a stable capability.\n\n- Standing-mandate automatic approvalIn implementation outside the stable snapshotas of 31 August 2026 stable snapshot\n\nA six-gate standing-mandate approval path is being implemented outside the stable public snapshot.\n\nLimitation It must not be presented as stable, production-complete, or available for the snapshot used by the numeric charts.\n\n- Mission mandate\n\n- Audit report\n\n- Resolution record\n\n- Approval provenance\n\n[Show in evidence graph · Standing-mandate automatic approval](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- ### Future direction\n\n1 capability\n\nAn intended direction without a current operational claim.\n\n- Fully autonomous multi-project engineeringFuture directionas of 31 August 2026 stable snapshot\n\nBroader multi-project autonomy is a future direction, not a current public capability.\n\nLimitation No autonomy score, deployment count, or completion date is approved.\n\n- Mission mandate\n\n- Work package and change scope\n\n- Approval provenance\n\n[Show in evidence graph · Fully autonomous multi-project engineering](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\n- ### Retained fallback\n\n1 capability\n\nA manual or rollback path deliberately remains available.\n\n- Manual fallbackRetainedas of 31 August 2026 stable snapshot\n\nManual fallback and rollback remain explicit parts of the operating model.\n\nLimitation Fallback availability does not prove that every rollback scenario is risk-free.\n\n- Mission mandate\n\n- Approval provenance\n\n- Promotion and closure record\n\n[Show in evidence graph · Manual fallback](https://atanasseri.com/projects/agentic-development-orchestrator#evidence)\n\nCapability status ladder · 9 capabilities · 4 status classesCurrent selection\n\nOperational in stable evidence\n\n6\n\nIn implementation outside the stable snapshot\n\n1\n\nFuture direction\n\n1\n\nRetained fallback\n\n1\n\nSelect a capability to highlight the evidence classes that support its public status.\n\nBasis: Current status · In implementation and Planned where marked · As of 31 August 2026. Status classes follow the approved capability record. No maturity score is derived.\n\nMethodology\n\n## How to read these numbers\n\nThe webpage uses one versioned snapshot of the repository's stable branch. Canonical audit reports supply review, round, time, verdict, File Count, and finding severity. Canonical resolution reports supply recorded finding dispositions. Repository file count comes from the stable Git tree. Active development outside the stable snapshot is excluded from numeric aggregates.\n\nAudit counts, finding counts, durations, and file counts are descriptive evidence. They do not prove causality, security, quality, completeness, productivity, or commercial value.\n\nData extracted 2 September 2026 from the stable snapshot committed 31 August 2026.\n\nSnapshot alias stable-2026-08-31 · dataset 1.0.0 · schema 1.0.0 · validation passed\n\nData basis\n\nReported\n\ncopied from a canonical record\n\nDerived\n\ncalculated from reported values using a documented formula\n\nInterpreted\n\nan analytical statement that is not itself a raw field\n\nCurrent status\n\nan implementation-maturity statement as of the page date\n\nHistorical exception\n\na record governed by an earlier process or incomparable condition\n\nMetric formulas\n\nReview count · Derived\n\nDistinct public Review aliases represented by canonical audit reports. 10\n\nAudit-report count · Reported\n\nCanonical audit-report files in the stable snapshot. 21\n\nFinding count · Derived\n\nCRITICAL + HIGH + MEDIUM across canonical reports. 0 + 56 + 62 = 118\n\nRecorded audit duration · Derived\n\nCompleted At − Started At, summed across 21 reports. 17,825 s = 297m 05s\n\nAudit File Count · Reported, derived multiple\n\nInteger recorded as File Count in each report; first measurable and latest. 81 → 329, 329 ÷ 81 = 4.06×\n\nRepository file count · Derived\n\nBlob entries in the recursive Git tree of the stable commit. 299\n\nPaired round comparison · Derived comparison\n\nRound 1 and Round 2 totals for Review 02 to Review 10. 62 → 52, difference −10\n\nRecorded disposition · Recorded\n\nDisposition recorded in the matching resolution report for each canonical finding. 113 FIXED, 3 ACCEPTED\\_RISK, 2 OWNER\\_DECISION\\_REQUIRED\n\nExclusions and exceptions\n\nActive-branch exclusion\n\nActive work outside the stable snapshot is excluded from all numeric aggregates. It appears only as the qualitative status “In implementation outside the stable snapshot”.\n\nAudit File Count versus repository blob count\n\nAudit File Count is an attested path count recorded by each report. Repository file count is the number of blobs in the stable Git tree (299). They never share one axis.\n\nRecorded disposition\n\nRecorded FIXED means the resolution report states that a fix was made. It does not mean every fix was independently re-audited after the final round.\n\nHistorical exception · R01.1\n\nIdentity or evidence conditions prevented a substantive audit. This is not a clean zero-finding report.\n\nHistorical exception · R01.3\n\nThis report belongs to an earlier governance process and does not imply that the current process permits an automatic third round.\n",
      "contentSha256": "9d478c59b080d58cd14104c2f1dac291ad582468a3f4a356dd902829b0b7e101"
    },
    {
      "url": "https://atanasseri.com/projects/h2learn",
      "route": "/projects/h2learn",
      "lastModified": "2026-09-08",
      "title": "H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product",
      "description": "A stakeholder-reviewed product prototype for discovering initiatives, organizations, and collaboration opportunities across the hydrogen learning ecosystem.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/h2learn.md",
      "headings": [
        {
          "level": 1,
          "text": "H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product"
        },
        {
          "level": 2,
          "text": "H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product"
        },
        {
          "level": 3,
          "text": "Objective"
        },
        {
          "level": 3,
          "text": "My Role"
        },
        {
          "level": 3,
          "text": "Process"
        },
        {
          "level": 3,
          "text": "Outcome & Impact"
        },
        {
          "level": 3,
          "text": "Reflection"
        }
      ],
      "links": [
        {
          "text": "All projects",
          "url": "https://atanasseri.com/projects"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/h2learn\nLast modified: 2026-09-08\n\n[All projects](https://atanasseri.com/projects)\n\n# H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product\n\nA stakeholder-reviewed product prototype for discovering initiatives, organizations, and collaboration opportunities across the hydrogen learning ecosystem.\n\nRole\n\nProduct Manager\n\n## H2Learn: From Ecosystem Ambiguity to an Initiative-Centered Product\n\nProduct ManagementSolution ArchitectureEcosystem DiscoveryHuman-in-the-LoopAI-Native Product\n\nH2Learn ecosystem map and prototype visualization\n\n### Objective\n\nMake knowledge, initiatives, organizations, and collaboration opportunities easier to discover across the hydrogen learning ecosystem.\n\n### My Role\n\nProduct Manager & Solutions Architect. I shaped the product direction, scope, user journeys, information architecture, discovery logic, prototype, and the relationship between product decisions and the underlying system design.\n\n### Process\n\nThe project began with a broad and ambiguous ecosystem challenge. I translated it into a product model connecting initiatives, organizations, knowledge, needs, offers, bottlenecks, and collaboration signals. The early direction explored explainable knowledge matchmaking. Through prototype development and stakeholder review, the strongest need became clearer: begin with an initiative-centered map that allows users to discover initiatives, see their connected organizations, and understand ecosystem relationships.\n\n### Outcome & Impact\n\nProduced a working, stakeholder-reviewed prototype and converted a broad challenge into a clearer initiative-centered product direction. The result demonstrates the product logic, geographic and network exploration, initiative–organization relationships, and governance considerations. This was a stakeholder-reviewed functional prototype, not a fully deployed production platform.\n\n### Reflection\n\nProduct ownership is not defending the first solution. It is creating enough clarity to test a direction, and changing that direction when evidence reveals a simpler and more valuable path.\n",
      "contentSha256": "8bfb1c8c4c7d97fff4a7622e32b97e26c93eab50755e63dfcea7529358b79fa2"
    },
    {
      "url": "https://atanasseri.com/projects/consumer-credit",
      "route": "/projects/consumer-credit",
      "lastModified": "2026-09-08",
      "title": "Consumer Credit: Turning a Fragmented Process into One Product System",
      "description": "An end-to-end consumer-credit lifecycle embedded in off-plan residential purchases.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/consumer-credit.md",
      "headings": [
        {
          "level": 1,
          "text": "Consumer Credit: Turning a Fragmented Process into One Product System"
        },
        {
          "level": 2,
          "text": "Consumer Credit: Turning a Fragmented Process into One Product System"
        },
        {
          "level": 3,
          "text": "Organization"
        },
        {
          "level": 3,
          "text": "Objective"
        },
        {
          "level": 3,
          "text": "My Role"
        },
        {
          "level": 3,
          "text": "Process"
        },
        {
          "level": 3,
          "text": "Outcome & Impact"
        },
        {
          "level": 3,
          "text": "Reflection"
        }
      ],
      "links": [
        {
          "text": "All projects",
          "url": "https://atanasseri.com/projects"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/consumer-credit\nLast modified: 2026-09-08\n\n[All projects](https://atanasseri.com/projects)\n\n# Consumer Credit: Turning a Fragmented Process into One Product System\n\nAn end-to-end consumer-credit lifecycle embedded in off-plan residential purchases.\n\nRole\n\nProduct Manager\n\n## Consumer Credit: Turning a Fragmented Process into One Product System\n\nConsumer CreditEnd-to-End Product OwnershipCredit RiskOperationsProperty-Secured Finance\n\nVisualization of consumer credit lifecycle\n\n### Organization\n\nMaskan Investment Group (MIG)\n\n### Objective\n\nDeliver a developer-financed, property-secured B2C credit product embedded in off-plan residential purchases within a business delivering approximately 1,400 units annually.\n\n### My Role\n\nProduct Manager for the end-to-end consumer-credit lifecycle. I coordinated execution across Credit Risk, Sales, Finance, Legal, Construction, Customer Service, and Collections.\n\n### Process\n\nConnected customer onboarding, affordability, underwriting, pricing, contracts, down payment, construction milestones, initial funding, repayment observation, property handover, final allocation, collateral release, exceptions, and recovery. Translated credit policies into structured business rules, approval gates, decision rights, handoffs, and operational workflows.\n\n### Outcome & Impact\n\nReduced the project setup-to-initial-funding cycle from approximately six months to three weeks (an estimated 88% reduction), and contributed to an approximately 23% reduction in defaults among customers progressing to final unit allocation.\n\n### Reflection\n\nRisk was not reduced by adding more isolated controls. It was reduced by making the complete lifecycle visible and redesigning how decisions, information, and accountability moved through the system.\n",
      "contentSha256": "8f4ea5bf264ea1c7e3572daa58080dc22f76c8643b604f6460b17839c2ebd1bd"
    },
    {
      "url": "https://atanasseri.com/projects/fundreg",
      "route": "/projects/fundreg",
      "lastModified": "2026-09-08",
      "title": "FundReg: Building Trust into Financial-Market Infrastructure",
      "description": "A centralized national mutual-fund ownership registry designed for integrity, oversight, and investor protection.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/fundreg.md",
      "headings": [
        {
          "level": 1,
          "text": "FundReg: Building Trust into Financial-Market Infrastructure"
        },
        {
          "level": 2,
          "text": "FundReg: Building Trust into Financial-Market Infrastructure"
        },
        {
          "level": 3,
          "text": "Organization"
        },
        {
          "level": 3,
          "text": "Objective"
        },
        {
          "level": 3,
          "text": "My Role"
        },
        {
          "level": 3,
          "text": "Process"
        },
        {
          "level": 3,
          "text": "Outcome & Impact"
        },
        {
          "level": 3,
          "text": "Reflection"
        }
      ],
      "links": [
        {
          "text": "All projects",
          "url": "https://atanasseri.com/projects"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/fundreg\nLast modified: 2026-09-08\n\n[All projects](https://atanasseri.com/projects)\n\n# FundReg: Building Trust into Financial-Market Infrastructure\n\nA centralized national mutual-fund ownership registry designed for integrity, oversight, and investor protection.\n\nRole\n\nProduct Manager for Post-Trade & Mutual Fund Registry Infrastructure\n\n## FundReg: Building Trust into Financial-Market Infrastructure\n\nFinancial InfrastructureMutual FundsPost-TradeRegulatory SystemsProduct Management\n\nVisualization of FundReg infrastructure\n\n### Organization\n\nCentral Securities Depository of Iran (CSDI)\n\n### Objective\n\nAddress fragmented mutual-fund ownership records across multiple software providers by contributing to a centralized national registry designed to improve integrity, transparency, oversight, and investor protection.\n\n### My Role\n\nProduct Manager for Post-Trade & Mutual Fund Registry Infrastructure. I worked across product requirements, system modeling, stakeholder coordination, regulatory considerations, operating logic, and implementation planning.\n\n### Process\n\nConnected ownership records, registry requirements, validation logic, legal and supervisory needs, operational workflows, and the transition from fragmented records toward a coherent central model.\n\n### Outcome & Impact\n\nContributed to the design and delivery of FundReg, a national mutual-fund registry serving approximately two million investors.\n\n### Reflection\n\nTrust in financial infrastructure is not created by a user interface. It is created by the relationships between records, controls, rules, governance, and accountable operations.\n",
      "contentSha256": "5923b5065b22d0a109ff364b9b6777edbf87d94f39d0aed68cb91c9114ac558a"
    },
    {
      "url": "https://atanasseri.com/projects/airsheet",
      "route": "/projects/airsheet",
      "lastModified": "2026-09-08",
      "title": "Airsheet: From Generic No-Code to AI-Native Nonprofit Operations",
      "description": "A focused AI-native operations product hypothesis for nonprofit teams.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/airsheet.md",
      "headings": [
        {
          "level": 1,
          "text": "Airsheet: From Generic No-Code to AI-Native Nonprofit Operations"
        },
        {
          "level": 2,
          "text": "Airsheet: From Generic No-Code to AI-Native Nonprofit Operations"
        },
        {
          "level": 3,
          "text": "Organization"
        },
        {
          "level": 3,
          "text": "Objective"
        },
        {
          "level": 3,
          "text": "My Role"
        },
        {
          "level": 3,
          "text": "Process"
        },
        {
          "level": 3,
          "text": "Outcome & Impact"
        },
        {
          "level": 3,
          "text": "Reflection"
        }
      ],
      "links": [
        {
          "text": "All projects",
          "url": "https://atanasseri.com/projects"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/airsheet\nLast modified: 2026-09-08\n\n[All projects](https://atanasseri.com/projects)\n\n# Airsheet: From Generic No-Code to AI-Native Nonprofit Operations\n\nA focused AI-native operations product hypothesis for nonprofit teams.\n\nRole\n\nFounder & Product Lead\n\n## Airsheet: From Generic No-Code to AI-Native Nonprofit Operations\n\nAI-Native ProductNonprofit OperationsProduct DiscoveryVenture BuildingHuman Review\n\nAirsheet AI-native operations visual\n\n### Organization\n\nSolofounders\n\n### Objective\n\nExplore how AI could help nonprofit teams interpret organizational information, surface operational priorities, and move from scattered data toward reviewable action.\n\n### My Role\n\nFounder & Product Lead, responsible for product direction, problem framing, user-value logic, prototype development, and pilot positioning.\n\n### Process\n\nThe initial concept began as a broad no-code platform. Product exploration revealed that generic flexibility weakened the value proposition. The direction shifted toward a more focused AI-native operations product for nonprofits, supported by a value-for-feedback pilot model.\n\n### Outcome & Impact\n\nEstablished a more focused product hypothesis, clearer target context, and pilot-oriented direction. It remains an evolving product initiative rather than a proven scaled business.\n\n### Reflection\n\nA pivot becomes valuable when it removes attractive but nonessential possibilities and brings the product closer to a specific problem worth solving.\n",
      "contentSha256": "4c132a94531ae2b34869be6157852e0ad08f7d5cee14f7bfcdcd20ddf98547e9"
    },
    {
      "url": "https://atanasseri.com/projects/gader",
      "route": "/projects/gader",
      "lastModified": "2026-09-08",
      "title": "Gader: Designing Technology That Moves into the Background",
      "description": "A local-first social product centered on nearby activities and real human connection.",
      "markdownUrl": "https://atanasseri.com/content/pages/projects/gader.md",
      "headings": [
        {
          "level": 1,
          "text": "Gader: Designing Technology That Moves into the Background"
        },
        {
          "level": 2,
          "text": "Gader: Designing Technology That Moves into the Background"
        },
        {
          "level": 3,
          "text": "Organization"
        },
        {
          "level": 3,
          "text": "Objective"
        },
        {
          "level": 3,
          "text": "My Role"
        },
        {
          "level": 3,
          "text": "Process"
        },
        {
          "level": 3,
          "text": "Outcome & Impact"
        },
        {
          "level": 3,
          "text": "Reflection"
        }
      ],
      "links": [
        {
          "text": "All projects",
          "url": "https://atanasseri.com/projects"
        }
      ],
      "markdown": "Source: https://atanasseri.com/projects/gader\nLast modified: 2026-09-08\n\n[All projects](https://atanasseri.com/projects)\n\n# Gader: Designing Technology That Moves into the Background\n\nA local-first social product centered on nearby activities and real human connection.\n\nRole\n\nFounder & Product Lead\n\n## Gader: Designing Technology That Moves into the Background\n\nLocal-First ProductSocial DiscoveryPWAAndroidAI-Native Product\n\nGader local-first social product visual\n\n### Organization\n\nSolofounders\n\n### Objective\n\nCreate a local-first social product centered on small nearby activities, safer discovery, repeat encounters, and real human connection.\n\n### My Role\n\nFounder & Product Lead, responsible for product concept, experience direction, product development, and the relationship between intelligent discovery and human interaction.\n\n### Process\n\nDesigned the experience around local micro-events and real-world participation. AI supports discovery and coordination in the background, while people, places, safety, and repeated interaction remain in the foreground.\n\n### Outcome & Impact\n\nDeveloped a live product experience across PWA and Android.\n\n### Reflection\n\nThe most human AI products may be the ones in which intelligence creates better conditions for connection, and then becomes almost invisible.\n",
      "contentSha256": "9cf7bb38ff694b8809315929658617a2dfeb6ae4b0121cce5cc3715170b69f2a"
    },
    {
      "url": "https://atanasseri.com/vision",
      "route": "/vision",
      "lastModified": "2026-08-21",
      "title": "The Next Edge",
      "description": "A perspective on building responsible products where finance, risk, technology, and human judgment meet.",
      "markdownUrl": "https://atanasseri.com/content/pages/vision.md",
      "headings": [
        {
          "level": 1,
          "text": "The Next Edge"
        },
        {
          "level": 2,
          "text": "Building Forward Without Pretending to See Everything"
        },
        {
          "level": 2,
          "text": "What I Am Building Toward"
        },
        {
          "level": 3,
          "text": "Make Complex Decisions Legible"
        },
        {
          "level": 3,
          "text": "Connect Growth and Risk"
        },
        {
          "level": 3,
          "text": "Extend Judgment, Not Replace It"
        },
        {
          "level": 3,
          "text": "A Direction, Not a Prediction"
        }
      ],
      "links": [
        {
          "text": "Explore My Work",
          "url": "https://atanasseri.com/projects"
        },
        {
          "text": "View My CV",
          "url": "https://atanasseri.com/cv"
        }
      ],
      "markdown": "Source: https://atanasseri.com/vision\nLast modified: 2026-08-21\n\n# The Next Edge\n\nThe future is not a destination waiting to be predicted. It is a system shaped by the decisions we make before the map is complete.\n\n## Building Forward Without Pretending to See Everything\n\nI want to build products where complexity is real, decisions have consequences, and technology must connect more than one part of the system.\n\nThat means creating clearer relationships between growth and risk, finance and product, strategy and execution, intelligent systems and human accountability.\n\nAI is part of how I work, not a substitute for how I think. I use it to explore more deeply, build faster, and operate with more leverage, while keeping judgment, evidence, and responsibility human.\n\n## What I Am Building Toward\n\n### Make Complex Decisions Legible\n\nBuild products that reveal assumptions, dependencies, risks, and trade-offs so that people can understand not only what the system recommends, but why.\n\n### Connect Growth and Risk\n\nDesign product systems in which speed, customer value, economics, operational reality, and risk are addressed together rather than handed between disconnected functions.\n\n### Extend Judgment, Not Replace It\n\nCreate AI-native products that expand the field of view, accelerate exploration, and support action while keeping consequential decisions reviewable and accountable.\n\n### A Direction, Not a Prediction\n\nI do not expect the next important problem to arrive with a complete brief. I expect it to emerge through weak signals, competing needs, connected risks, and incomplete evidence.\n\nThat is the work I am preparing for: finding the structure inside uncertainty and turning it into a direction people can execute.\n\n[Explore My Work](https://atanasseri.com/projects)[View My CV](https://atanasseri.com/cv)\n",
      "contentSha256": "02cc71ee7115ddb4e8c0ead660a9560aebbb05f37637c6226e82349953812565"
    },
    {
      "url": "https://atanasseri.com/cv",
      "route": "/cv",
      "lastModified": "2026-09-08",
      "title": "Ata Nasseri",
      "description": "Experience, education, certifications, and skills in product management, financial infrastructure, consumer credit, risk, analytics, and AI-native products.",
      "markdownUrl": "https://atanasseri.com/content/pages/cv.md",
      "headings": [
        {
          "level": 1,
          "text": "Ata Nasseri"
        },
        {
          "level": 2,
          "text": "Professional Experience"
        },
        {
          "level": 3,
          "text": "Product Manager & Solutions Architect | H2Learn"
        },
        {
          "level": 3,
          "text": "Founder & Product Lead | AI-Native Venture Building"
        },
        {
          "level": 3,
          "text": "Alternative Investments Consultant | Market Risk, Futures & Options"
        },
        {
          "level": 3,
          "text": "Product Manager – Consumer Credit"
        },
        {
          "level": 3,
          "text": "Product Manager | Post-Trade & Mutual Fund Registry Infrastructure"
        },
        {
          "level": 3,
          "text": "CSDI Representative | Asia Fund Standardization Forum (AFSF)"
        },
        {
          "level": 3,
          "text": "CCP Risk Model Validator & Participant Credit Risk Specialist"
        },
        {
          "level": 3,
          "text": "Financial Market Infrastructure (FMI) Product & Risk Specialist"
        },
        {
          "level": 3,
          "text": "Business Development Advisor"
        },
        {
          "level": 3,
          "text": "Co-Founder & Asset Manager"
        },
        {
          "level": 3,
          "text": "Economic Journalist & Editorial Writer"
        },
        {
          "level": 3,
          "text": "Business Development Manager"
        },
        {
          "level": 3,
          "text": "Co-Founder & CFO"
        },
        {
          "level": 3,
          "text": "Editor in Chief"
        },
        {
          "level": 3,
          "text": "Chief Business Development Officer"
        },
        {
          "level": 2,
          "text": "Education"
        },
        {
          "level": 3,
          "text": "MBA – Entrepreneurship & Business Administration"
        },
        {
          "level": 3,
          "text": "BSc – Electrical, Electronics & Communications Engineering"
        },
        {
          "level": 2,
          "text": "Certifications"
        },
        {
          "level": 2,
          "text": "Technical & Analytical Skills"
        },
        {
          "level": 2,
          "text": "Product & Strategic Skills"
        },
        {
          "level": 2,
          "text": "Languages"
        },
        {
          "level": 2,
          "text": "Awards & Honors"
        }
      ],
      "links": [
        {
          "text": "contact@atanasseri.com",
          "url": "mailto:contact@atanasseri.com"
        },
        {
          "text": "linkedin.com/in/ata-nasseri",
          "url": "https://www.linkedin.com/in/ata-nasseri"
        },
        {
          "text": "github.com/Atanasseri",
          "url": "https://github.com/Atanasseri"
        },
        {
          "text": "Contact Ata",
          "url": "https://atanasseri.com/contact"
        }
      ],
      "markdown": "Source: https://atanasseri.com/cv\nLast modified: 2026-09-08\n\n# Ata Nasseri\n\nProduct Manager | FinTech & Consumer Credit | End-to-End Product Ownership, Risk & AI-Native Product Development | FRM\n\nThe Randstad, Netherlands [contact@atanasseri.com](mailto:contact@atanasseri.com) [linkedin.com/in/ata-nasseri](https://www.linkedin.com/in/ata-nasseri) [github.com/Atanasseri](https://github.com/Atanasseri)\n\nI build at the edge of uncertainty.\n\nMarkets, credit, startups, and AI share one truth: the future never arrives with a complete map. Signals are scattered. Risks are connected. The problem is rarely as simple as it first appears.\n\nThat is where I create the most value.\n\nI do not wait for perfect information. I make assumptions visible, identify the decisions that matter, and move. I look at the whole system, the user, economics, risk, data, operations, and consequences, then turn ambiguity into a clear product direction and an executable path.\n\nMy background crosses consumer credit, financial-market infrastructure, risk management, venture building, and AI-native product development. This allows me to connect worlds that are often managed separately: growth and risk, finance and product, strategy and execution, human judgment and intelligent systems.\n\nTo me, product ownership is not moving tickets through a backlog. It is owning the problem end to end: asking the questions others miss, making hard trade-offs, aligning people with different incentives, and staying accountable for the outcome.\n\nIn consumer credit, this approach helped turn a fragmented process into one operating model, reduce the setup-to-initial-funding cycle from about six months to three weeks, and contribute to an approximately 23% reduction in defaults among customers progressing to final unit allocation.\n\nIn H2Learn, it meant turning an ambiguous ecosystem challenge into product strategy, explainable system architecture, a working prototype, and, when the evidence changed, a simpler and more valuable product direction.\n\nAI is part of how I work, not a substitute for how I think. I use it to explore deeper, build faster, and operate with more leverage, while keeping judgment, evidence, and accountability human.\n\nI am most valuable when the problem matters, the path is unclear, and the cost of a shallow answer is high.\n\n## Professional Experience\n\n### Product Manager & Solutions Architect | H2Learn\n\nAmsterdam University of Applied Sciences\n\nAmsterdam | February 2026 - Present\n\n- Led and shaped the product design and solution architecture of H2Learn, an explainable, human-in-the-loop platform designed to make knowledge, projects, and collaboration opportunities easier to discover across the hydrogen learning ecosystem.\n\n- The project began with a broad and ambiguous challenge. I turned it into a clear product direction, user journey, data architecture, and working prototype.\n\n- Defined the product vision, scope, and value proposition.\n\n- Built the end-to-end data-to-match logic, translating structured inputs into profile signals, explainable relationships, ranked matches, and network views.\n\n- Designed the onboarding, discovery, network, and admin/governance workflows.\n\n- Worked with the team and stakeholders to test the prototype, identify user and data risks, and turn feedback into prioritised improvements.\n\n- Drove the product's evolution from broad knowledge matchmaking to a simpler, initiative-first map aligned with the partner's immediate need.\n\n- AI is part of how I work, not a substitute for how I think. I used it to explore deeper, accelerate research, documentation, prototyping, and implementation, and build faster, while keeping product judgment, evidence, validation, and accountability human.\n\n- The result was a stakeholder-reviewed functional prototype and a deployable initiative map with a clearer scope, stronger governance, and a more practical path forward.\n\n### Founder & Product Lead | AI-Native Venture Building\n\nSolofounders\n\nRotterdam | January 2025 - Present\n\n- Founded Solofounders as a hands-on venture studio where very small teams use AI to turn complex ideas and market shifts into focused products.\n\n- I currently lead two lean product teams, Airsheet and Gader, across product strategy, architecture, business model, and execution.\n\n- At Airsheet, I recognised that AI was rapidly commoditising generic no-code app building and led an end-to-end pivot from a horizontal platform toward an AI-native operations product for nonprofits. I helped redefine the target segment, value proposition, core workflows, and product architecture, positioning AI as the operating layer for turning organisational data into useful actions. The product is now in pilot through a value-for-feedback model designed to create immediate value for nonprofit partners while validating a repeatable path to scale.\n\n- At Gader, I guide a two-person team building a live, local-first social product for real-world connection. I helped shape its multi-sided business model and product direction: simple micro-events in public places, designed around safety and repeat encounters rather than swiping or endless online interaction. The PWA and Android product are live, with AI designed to support discovery, safety, and repeat connection quietly in the background.\n\n- Together, these ventures reflect how I work: recognising change early, making focused product choices, and helping small teams move from ambiguity to pilot and live products.\n\n### Alternative Investments Consultant | Market Risk, Futures & Options\n\nIRIC-CO\n\nThe Randstad, Netherlands | September 2022 - August 2024\n\n- Advised companies on hedging commodity-price exposures through exchange-traded futures and options, with a focus on protecting cash flows, liquidity, and financial resilience.\n\n- Mapped underlying commercial exposures and risk objectives to instrument selection, contract maturity, position size, and hedge ratio.\n\n- Directly monitored futures and options positions on the commodity exchange, assessing mark-to-market performance, hedge effectiveness, basis risk, margin requirements, liquidity, and rollover needs.\n\n- Used scenario and sensitivity analysis to evaluate adverse price and volatility movements and recommended adjustments to hedge coverage, position limits, and liquidity requirements.\n\n- Assessed the trade-off between the linear protection of futures and the asymmetric downside protection of options, considering premium cost and residual exposure.\n\n- This work showed how commodity-price shocks, hedge losses, and margin calls can weaken cash flow and debt-servicing capacity, connecting market-risk management with broader credit resilience.\n\n### Product Manager – Consumer Credit\n\nMaskan Investment Group (MIG)\n\nTehran | September 2021 - August 2022\n\n- Owned the end-to-end delivery of a developer-financed, property-secured B2C credit product embedded in off-plan home purchases within a residential business delivering approximately 1,400 units annually.\n\n- Led cross-functional execution across Credit Risk, Sales, Finance, Legal, Construction, Customer Service, and Collections, aligning policies, decision rights, approval gates, handoffs, and exception paths across origination, servicing, and recovery.\n\n- Translated affordability, underwriting, pricing, repayment, and restructuring policies into structured business rules and operational workflows.\n\n- Integrated the credit lifecycle with unit reservation, down payment, construction milestones, property handover, title transfer, and collateral release.\n\n- Used the first 12 months of repayment behaviour as a structured risk-observation period, enabling centralised assessment and enhanced review of higher-risk cases before final unit allocation.\n\n- Outcomes: Reduced the project setup-to-initial-funding cycle from approximately six months to three weeks, an estimated 88% reduction, and contributed to an approximately 23% reduction in defaults among customers progressing to final unit allocation.\n\n### Product Manager | Post-Trade & Mutual Fund Registry Infrastructure\n\nCentral Securities Depository of Iran\n\nTehran Province, Iran | April 2019 - August 2021\n\nLed product management for FundReg, a national-scale capital-market infrastructure platform designed to centralize, structure, and safeguard ownership records across a subscription/redemption-based mutual-fund market serving approximately 2 million investors.\n\nThe platform addressed a critical market-infrastructure challenge: mutual-fund ownership data was fragmented across software providers, creating operational, legal, supervisory, and systemic risks for the capital market.\n\n- Worked directly with the Securities and Exchange Organization (SEO), including its Risk Committee and Investment Funds Supervision Directorate, to address regulatory requirements throughout the approval process.\n\n- Translated regulatory, legal, and risk requirements into product rules, data controls, and operational workflows.\n\n- Shaped the CSD-based registry model after reviewing international approaches to mutual-fund infrastructure.\n\n- Redesigned the onboarding journey when e-KYC through the national identity-verification system became a regulatory requirement.\n\n- Coordinated the regulator, fund operators, legal and risk stakeholders, and technology teams from product definition through implementation and pilot.\n\nFundReg received regulatory approval and entered the pilot stage. It was designed to provide a trusted central registry, strengthen regulatory oversight, and better protect investor records.\n\n### CSDI Representative | Asia Fund Standardization Forum (AFSF)\n\nCentral Securities Depository of Iran\n\nIndonesia | September 2018 - August 2019\n\nRepresented CSDI in the Asia Fund Standardization Forum, bringing together central securities depositories and financial-market infrastructure institutions from ten Asian markets.\n\nCompared fund-market structures, regulatory approaches, and platform models across participating markets, with a focus on investor registration, subscription, redemption, and settlement.\n\nUsed this international benchmark to shape FundReg's CSD-based registry model and personally presented the model to AFSF members, explaining:\n\n- The risks created by fragmented mutual-fund ownership records.\n\n- The rationale for moving to a trusted central registry.\n\n- How the proposed model would support fund operations, regulatory oversight, and investor protection.\n\n- The model became the foundation for FundReg, which later received regulatory approval and entered the pilot stage.\n\nThis experience connected international benchmarking with a concrete national-scale product and gave me direct experience representing and presenting a regulated financial-infrastructure model to international stakeholders.\n\n### CCP Risk Model Validator & Participant Credit Risk Specialist\n\nCentral Securities Depository of Iran\n\nTehran Province, Iran | April 2018 - March 2019\n\nWorked across two connected areas of financial market infrastructure risk: independent validation of CCP risk methodologies and ongoing counterparty credit-risk management of broker-dealer participants.\n\n- Validated CCP exposure, margin, collateral and stress-testing methodologies through backtesting, sensitivity analysis and scenario-based assessment.\n\n- Managed participant credit limits and monitored daily settlement exposures arising from T+2/T+3 obligations, including limit utilisation, settlement performance and early-warning indicators.\n\n- Conducted periodic and ad-hoc credit reviews of broker-dealers, considering their financial condition, settlement behaviour, customer-related exposures and available credit support.\n\n- Assessed bank guarantees and letters of credit for coverage, validity, maturity and issuer risk, and used the results to support credit-limit recalibration.\n\n- Translated quantitative model outputs and participant-level risk signals into practical recommendations on limits, collateral requirements and risk controls.\n\n- Documented findings and worked with risk, clearing, settlement, technology and regulatory stakeholders to strengthen the CCP/CSD financial risk framework.\n\n### Financial Market Infrastructure (FMI) Product & Risk Specialist\n\nCentral Securities Depository of Iran\n\nTehran Province, Iran | March 2017 - April 2018\n\nWorked on post-trade and financial market infrastructure initiatives across mutual fund operations, central counterparty (CCP) clearing infrastructure, risk management, and cross-border investment models.\n\nKey contributions:\n\n- Contributed to the early development of a CSD-based mutual fund infrastructure platform for organizing and dematerializing subscription/redemption-based fund operations.\n\n- Supported the design of process flows and requirements for mutual fund registry, ownership-record handling, and operational standardization.\n\n- Worked on the CSDI risk management initiative connected to the implementation of central counterparty (CCP) clearing infrastructure.\n\n- Helped analyze CCP-related operational and risk-management requirements, including clearing workflows, risk controls, stakeholder coordination, and infrastructure readiness.\n\n- Participated in the 'Interface Model' project, exploring fund-based structures for indirect foreign investment through third-party jurisdictions.\n\n- Built a strong foundation in regulated financial market infrastructure, connecting CSD operations, CCP infrastructure, post-trade systems, product development, and financial risk management.\n\n### Business Development Advisor\n\nIust Start-up Camp\n\nFebruary 2016 - September 2018\n\n- Coaching business model generation and start-up valuation workshops\n\n- Start-up financing consultant\n\n- Start-up business model development consultant\n\n- At Iran university of science and technology(IUST)\n\n### Co-Founder & Asset Manager\n\nTahlilgaranebazar Group\n\nSeptember 2013 - September 2016\n\nAs Co-Founder and Asset Manager at Tahlilgaranebazar Group, I transitioned from economic journalism to hands-on investment strategy, bringing market insights to action. My core responsibilities include:\n\n- Co-founding the firm and serving as Chief Business Development Officer, responsible for driving growth strategies, forming partnerships, and defining the company's market position.\n\n- Working as an Asset Manager and Investment Advisor, managing client portfolios with a focus on capital preservation and long-term value creation.\n\n- Conducting in-depth capital market analysis, interpreting macroeconomic trends, and turning complex data into actionable investment insights.\n\n- Designing client-focused investment strategies based on risk profiles, market conditions, and long-term goals.\n\n- Leveraging my background in economic journalism to communicate investment strategies clearly and build trust with clients and partners.\n\nThis role represents the convergence of analytical expertise and strategic leadership, rooted in a deep understanding of financial markets and economic dynamics.\n\n### Economic Journalist & Editorial Writer\n\nKhorasan Newspaper\n\nAugust 2012 - September 2013\n\nAs a senior member of the economic editorial team at Khorasan Newspaper (the third most widely read newspaper in Iran), I contributed to the newspaper's core economic content strategy and reporting. My key responsibilities included:\n\n- Serving as a senior editorial writer for the economy section, producing opinion pieces and analytical columns on pressing economic issues.\n\n- Acting as a capital market analyst, delivering data-driven insights and commentary on trends in the Tehran Stock Exchange and related sectors.\n\n- Providing regular analyses of the gold and currency markets, with a focus on accessibility and clarity for the general readership.\n\n- Collaborating with the editorial team to develop innovative topic ideas tailored to public interest and national economic developments.\n\n- Participating in editorial meetings to shape the economic section's direction and ensure alignment with journalistic standards.\n\n- This role refined my expertise in economic journalism, public communication, and market analysis, while deepening my ability to translate complex financial data into accessible narratives.\n\n### Business Development Manager\n\nIRIC-CO\n\nFebruary 2011 - January 2013\n\n### Co-Founder & CFO\n\nIRIC-CO\n\nFebruary 2010 - February 2011\n\n### Editor in Chief\n\nNegareh Magazine\n\nMashhad, Razavi Khorasan, Iran | January 2010 - August 2010\n\nAs the Editor-in-Chief of Negareh Magazine, a monthly publication tailored to high school students, I led the editorial process from concept to publication. My key responsibilities included:\n\n- Developing and presenting article ideas to the editorial board, and guiding the selection of engaging and relevant topics.\n\n- Overseeing graphic design and layout, ensuring visually appealing and cohesive magazine spreads.\n\n- Collaborating with the creative team to conceptualize impactful and content-rich cover designs.\n\n- Actively participating in reader council meetings to gather feedback and insights, and integrating constructive critiques into future issues.\n\n- Facilitating communication between writers, designers, and stakeholders to maintain editorial quality and consistency.\n\nThis role honed my skills in creative leadership, content strategy, visual storytelling, and audience engagement.\n\n### Chief Business Development Officer\n\nMojafarin\n\nAugust 2008 - January 2010\n\n## Education\n\n### MBA – Entrepreneurship & Business Administration\n\nIran University of Science and Technology\n\nRanked 1st in program\n\n### BSc – Electrical, Electronics & Communications Engineering\n\nSadjad University of Technology\n\n## Certifications\n\n- Certified Financial Risk Manager (FRM)\n\n- Banking Digitization\n\n- Business Analytics\n\n- Financial Modeling\n\n- Forecasting and Predictive Analytics\n\n- Accredited in Business Valuation (ABV)\n\n## Technical & Analytical Skills\n\nComplex Systems AnalysisFinancial Risk ManagementRisk Modeling & ValidationFinancial Market InfrastructureBusiness AnalyticsFinancial ModelingForecasting & Predictive AnalyticsSQLPython\n\n## Product & Strategic Skills\n\nDecision-Making Under UncertaintyEnd-to-End Product OwnershipProduct Strategy & DiscoverySolution ArchitectureStakeholder AlignmentAI-Native Product Development\n\n## Languages\n\n- Persian – Native\n\n- English – Professional\n\n- Dutch – Basic Proficiency\n\n## Awards & Honors\n\n- Ranked 1st in MBA cohort – IUST\n\n- Top 1% nationwide in MSc Management entrance exam (Iran)\n\n[Contact Ata](https://atanasseri.com/contact)\n",
      "contentSha256": "ba03dad2391d716dc571f71101e88c34f536d5fa4228d16a571f6b599f587ca1"
    },
    {
      "url": "https://atanasseri.com/contact",
      "route": "/contact",
      "lastModified": "2026-08-21",
      "title": "Start with the Problem",
      "description": "Contact Ata Nasseri about product leadership, FinTech, consumer credit, financial infrastructure, risk, or AI-native product development.",
      "markdownUrl": "https://atanasseri.com/content/pages/contact.md",
      "headings": [
        {
          "level": 1,
          "text": "Start with the Problem"
        },
        {
          "level": 2,
          "text": "What are you trying to make clearer?"
        },
        {
          "level": 2,
          "text": "Contact Details"
        },
        {
          "level": 2,
          "text": "Collaboration Focus"
        }
      ],
      "links": [
        {
          "text": "contact@atanasseri.com",
          "url": "mailto:contact@atanasseri.com"
        },
        {
          "text": "Connect on LinkedIn",
          "url": "https://www.linkedin.com/in/ata-nasseri"
        },
        {
          "text": "View Full CV",
          "url": "https://atanasseri.com/cv"
        }
      ],
      "markdown": "Source: https://atanasseri.com/contact\nLast modified: 2026-08-21\n\n# Start with the Problem\n\nThe most useful conversations often begin before the problem has been fully defined. If you are working on a product where the path is unclear, the risks are connected, or strategy and execution keep separating from each other, I would be interested in hearing what you are trying to build.\n\n## What are you trying to make clearer?\n\nShare the problem, the context, and what currently feels uncertain. You do not need to arrive with a finished brief.\n\n## Contact Details\n\nOther ways to get in touch or view my profile.\n\n[contact@atanasseri.com](mailto:contact@atanasseri.com)[Connect on LinkedIn](https://www.linkedin.com/in/ata-nasseri)[View Full CV](https://atanasseri.com/cv)\n\n## Collaboration Focus\n\nI welcome conversations about product leadership, consumer credit, financial infrastructure, risk-aware product development, AI-native products, ecosystem discovery, and complex cross-functional systems.\n",
      "contentSha256": "db067149322297af212f5632d1aad2e2b58bfa387bfe4458dd7ad250626d32ec"
    },
    {
      "url": "https://atanasseri.com/privacy",
      "route": "/privacy",
      "lastModified": "2026-08-21",
      "title": "Privacy",
      "description": "How Ata Nasseri's website handles contact details, anti-abuse checks, optional analytics, local preferences, and external links.",
      "markdownUrl": "https://atanasseri.com/content/pages/privacy.md",
      "headings": [
        {
          "level": 1,
          "text": "Privacy"
        },
        {
          "level": 2,
          "text": "Contact enquiries"
        },
        {
          "level": 2,
          "text": "Purpose and retention"
        },
        {
          "level": 2,
          "text": "Verification and abuse prevention"
        },
        {
          "level": 2,
          "text": "Service providers and transfers"
        },
        {
          "level": 2,
          "text": "Optional analytics"
        },
        {
          "level": 2,
          "text": "Local preferences and external links"
        },
        {
          "level": 2,
          "text": "Your choices and questions"
        }
      ],
      "links": [
        {
          "text": "contact@atanasseri.com",
          "url": "mailto:contact@atanasseri.com"
        }
      ],
      "markdown": "Source: https://atanasseri.com/privacy\nLast modified: 2026-08-21\n\n# Privacy\n\nA concise description of what this website actually does.\n\n## Contact enquiries\n\nThe Contact page asks for your full name, email address, and message so the enquiry can be read, managed, and answered. Please do not include confidential or sensitive personal information.\n\nIn direct-email mode, the form opens a draft in your own email application and this website does not store the form contents. When API submission is enabled, an accepted message is stored in Supabase before a notification is attempted through Resend and received through Google Workspace. A notification failure does not erase the stored enquiry.\n\n## Purpose and retention\n\nContact details are used only to assess and respond to an enquiry and to maintain necessary correspondence. The intended legal basis is the legitimate interest in responding to enquiries and, where applicable, taking steps you request before entering an agreement.\n\nOrdinary enquiries are scheduled for automatic deletion 12 months after the last relevant interaction recorded for the enquiry. If correspondence becomes a contractual or other required business record, it moves to the applicable record-keeping process instead of remaining indefinitely in the website inbox.\n\n## Verification and abuse prevention\n\nAPI submissions use Cloudflare Turnstile, a hidden trap field, an elapsed-time signal, a random request identifier, and short-lived rate limits. This application does not store raw IP addresses or browser fingerprints in its database or application logs. It derives keyed, pseudonymous rate-limit signals that expire within 24 hours.\n\nCloudflare and other infrastructure providers may still process network identifiers and operational telemetry under their own terms. A keyed hash is pseudonymous data, not anonymous data.\n\n## Service providers and transfers\n\nHostinger serves the website. Supabase stores accepted enquiries and provides server functions. Cloudflare provides Turnstile verification. Resend attempts the owner notification, and Google Workspace receives and holds email correspondence. These providers may process content and operational telemetry in the locations and under the safeguards described in their current privacy and data-processing terms, including transfers outside the European Economic Area where applicable.\n\n## Optional analytics\n\nAnalytics are disabled in the default release package. If the owner configures Google Analytics, it remains off until you explicitly allow it. A consent preference may then be stored in your browser so the site can remember your choice. No advertising consent is requested or granted by this site.\n\n## Local preferences and external links\n\nApart from an optional analytics choice, this site does not use browser storage for public tracking. Links to email, LinkedIn, and the separate AEAS website leave this site and are governed by those services' own privacy practices.\n\n## Your choices and questions\n\nYou may ask whether your information is held and request access, correction, deletion, restriction, or object to processing where those rights apply. You may also raise a concern with your local data-protection authority.\n\nFor a privacy request, email [contact@atanasseri.com](mailto:contact@atanasseri.com).\n",
      "contentSha256": "a80c3af3830f743b447b3ba6c66c30a1b9e84516a1e147b19d55d66e4327f2a8"
    }
  ],
  "studies": [
    {
      "title": "Agentic Development Orchestrator",
      "url": "https://atanasseri.com/projects/agentic-development-orchestrator",
      "snapshot": "stable-2026-08-31",
      "datasets": [
        {
          "name": "public-data-manifest.json",
          "url": "https://atanasseri.com/content/automation-coding/public-data-manifest.json",
          "sha256": "336422cb6405bafe50f0dc3736da595f0c5f1319c68713e078a8b4897e9e1893"
        },
        {
          "name": "audit-rounds.json",
          "url": "https://atanasseri.com/content/automation-coding/audit-rounds.json",
          "sha256": "fb3f386a3f1b69f9b2dc75fafec133988745cfaa5d0487519babfc571d503410"
        },
        {
          "name": "finding-dispositions.json",
          "url": "https://atanasseri.com/content/automation-coding/finding-dispositions.json",
          "sha256": "0ce7cac01e585118a056d2a05972fbaab4f1afa7e7470b4c18acb73498644c4b"
        },
        {
          "name": "approval-gates.json",
          "url": "https://atanasseri.com/content/automation-coding/approval-gates.json",
          "sha256": "da9f047a890a021dc94cf447265a711e4dd8ab57fdeccc75ba35e07790d9e53d"
        },
        {
          "name": "evidence-chain.json",
          "url": "https://atanasseri.com/content/automation-coding/evidence-chain.json",
          "sha256": "2ec65af0b53e6bebee1384ef0b093730803383a7c6ee2fe22301b9c74a90c0f6"
        },
        {
          "name": "capability-status.json",
          "url": "https://atanasseri.com/content/automation-coding/capability-status.json",
          "sha256": "42f294a9c428ed588be094cd73dfd913866eb40c7371fd37617ef3c3256ab165"
        }
      ]
    }
  ],
  "externalReferences": [
    {
      "title": "AEAS",
      "url": "https://aeas.atanasseri.com/"
    }
  ]
}