{"data":[{"amo_id":"AMO-W-000047","title":"Prepare a Period-End Close for Controller Review","slug":"prepare-a-period-end-close-for-controller-review","summary":"Use this for coordinating a source-backed close review across data, reconciliations, entries, reporting ties and unresolved matters before a controller decides.","outcome":"A controller review package linking balances and proposed adjustments to evidence, showing unresolved items and actual human dispositions. It does not post journals, close an ERP, issue statements or provide an audit opinion.","step_count":7,"url":"https:\/\/amo.ng\/workflows\/prepare-a-period-end-close-for-controller-review","public_url":"https:\/\/amo.ng\/workflows\/prepare-a-period-end-close-for-controller-review"},{"amo_id":"AMO-W-000046","title":"Build and Challenge a Driver-Based Budget and Rolling Forecast","slug":"build-and-challenge-a-driver-based-budget-and-rolling-forecast","summary":"Use this for building a reviewed planning package from authorised actuals and operational drivers, with manual model construction, assumption challenge, cash review and human approval.","outcome":"A versioned driver\/assumption register, externally calculated linked forecast, evidence-qualified movement and cash review, leadership commentary and an explicit human decision record. Amo.ng does not construct or approve an ERP\/planning model by itself.","step_count":7,"url":"https:\/\/amo.ng\/workflows\/build-and-challenge-a-driver-based-budget-and-rolling-forecast","public_url":"https:\/\/amo.ng\/workflows\/build-and-challenge-a-driver-based-budget-and-rolling-forecast"},{"amo_id":"AMO-W-000045","title":"Develop Customer Interview Evidence for a Positioning Decision","slug":"develop-customer-interview-evidence-for-a-positioning-decision","summary":"Develop a research question and interview protocol, pause for authorised fieldwork and human analysis, then challenge interpretations and compare evidence-bounded positioning options.","outcome":"A traceable research-to-positioning working record: approved question and method, protocol and actual fieldwork evidence where available, reviewed interpretations, positioning options and a human decision or explicit evidence gap. AI does not interview participants, validate a market or approve positioning.","step_count":4,"url":"https:\/\/amo.ng\/workflows\/develop-customer-interview-evidence-for-a-positioning-decision","public_url":"https:\/\/amo.ng\/workflows\/develop-customer-interview-evidence-for-a-positioning-decision"},{"amo_id":"AMO-W-000040","title":"Launch a Governed AI Support Triage Pilot","slug":"launch-a-governed-ai-support-triage-pilot","summary":"Review an already-approved, implemented support-triage pilot for limited activation. Check current data permissions, operational readiness, escalation rehearsal evidence and human authority, then record a go\/no-go decision with monitoring and rollback handoff. This Workflow does not design, build or activate the pilot.","outcome":"An operational launch-review record tied to the exact implemented pilot and approved scope: privacy\/authority disposition, readiness deltas, escalation and human-review evidence, unresolved blockers, an accountable activation decision and monitoring\/rollback responsibilities. No production routing, sending or activation is performed by this Workflow.","step_count":4,"url":"https:\/\/amo.ng\/workflows\/launch-a-governed-ai-support-triage-pilot","public_url":"https:\/\/amo.ng\/workflows\/launch-a-governed-ai-support-triage-pilot"},{"amo_id":"AMO-W-000042","title":"Build a Governed KPI Dashboard from Approved Metric Definitions","slug":"build-a-governed-kpi-dashboard-from-approved-metric-definitions","summary":"Translate already-approved metric definitions into a SQL-backed internal dashboard, with source-field mapping, authorized implementation, query-result reconciliation and an accountable release review. Metric definition approval and recurring report automation are outside this Workflow.","outcome":"A dashboard change set and release-review record tracing each approved metric through source fields, query stages, dashboard components and reconciliation evidence. Includes access and data-state tests, unresolved variances, decision-use restrictions, monitoring and rollback handoff. Publication or deployment is a separate authorized action.","step_count":5,"url":"https:\/\/amo.ng\/workflows\/build-a-governed-kpi-dashboard-from-approved-metric-definitions","public_url":"https:\/\/amo.ng\/workflows\/build-a-governed-kpi-dashboard-from-approved-metric-definitions"},{"amo_id":"AMO-W-000044","title":"Evidence-Controlled Internal Audit Working Paper","slug":"evidence-controlled-internal-audit-working-paper","summary":"Prepare a bounded working paper from permitted sources, reviewed scope and test design, evidence extraction, human analysis and challenged conclusions.","outcome":"A human-reviewed working-paper draft and disclosure record with evidence locators, limitations, approved carry-forward and unperformed work visible; no audit opinion or automatic closure.","step_count":6,"url":"https:\/\/amo.ng\/workflows\/evidence-controlled-internal-audit-working-paper","public_url":"https:\/\/amo.ng\/workflows\/evidence-controlled-internal-audit-working-paper"},{"amo_id":"AMO-W-000041","title":"Safely Build and Review a Multi-Tenant Laravel Feature","slug":"safely-build-and-review-a-multi-tenant-laravel-feature","summary":"Plan, implement, and review one approved multi-tenant SaaS feature with migration safety, authorization coverage, test evidence, pull-request review, and deployment readiness controls.","outcome":"A review-ready, bounded multi-tenant Laravel change with approved tenancy rules, migration and policy review, synthetic cross-tenant evidence, actual test results, unresolved limitations and a human-owned release\/rollback handoff. It is not an automatic merge or deployment decision.","step_count":6,"url":"https:\/\/amo.ng\/workflows\/safely-build-and-review-a-multi-tenant-laravel-feature","public_url":"https:\/\/amo.ng\/workflows\/safely-build-and-review-a-multi-tenant-laravel-feature"},{"amo_id":"AMO-W-000039","title":"Safely Plan, Build, Review, and Release a High-Risk Laravel Feature","slug":"safely-plan-build-review-and-release-a-high-risk-laravel-feature","summary":"Prepare a Laravel repository for AI-assisted coding, plan a complex feature, control migration and rollout risk, implement only within approved scope, review the pull request, and produce deployment-readiness evidence.","outcome":"A bounded, authorized Laravel implementation with repository evidence, applicable migration and feature-flag controls, actual verification results, independent change review and a human-owned release\/rollback handoff. Planning is not implementation, and this Workflow does not itself authorize deployment.","step_count":7,"url":"https:\/\/amo.ng\/workflows\/safely-plan-build-review-and-release-a-high-risk-laravel-feature","public_url":"https:\/\/amo.ng\/workflows\/safely-plan-build-review-and-release-a-high-risk-laravel-feature"},{"amo_id":"AMO-W-000037","title":"Build and Verify a Tenant-Scoped Paid Booking Slice","slug":"build-verify-tenant-scoped-paid-booking-slice","summary":"Implement one tenant-isolated paid booking journey through identity, availability\/reservation, hosted sandbox checkout, payment testing, security review, and release controls.","outcome":"Tenant-boundary map, booking\/order state transitions, repository\/schema manifests, cross-tenant and concurrency tests, hosted-checkout\/webhook reconciliation, payment\/security findings, disabled fulfilment evidence, rollback and release-owner package.","step_count":6,"url":"https:\/\/amo.ng\/workflows\/build-verify-tenant-scoped-paid-booking-slice","public_url":"https:\/\/amo.ng\/workflows\/build-verify-tenant-scoped-paid-booking-slice"},{"amo_id":"AMO-W-000036","title":"Build and Verify an Offline Searchable Directory PWA","slug":"build-verify-offline-searchable-directory-pwa","summary":"Implement an approved searchable directory, add bounded offline PWA behavior, protect its API contract, repair confirmed accessibility regressions, and prepare production verification and rollback controls.","outcome":"Directory and PWA change manifests, data\/search\/pagination contract, offline\/sync state model, API regression suite, accessibility repair\/verification record, cross-device test evidence, cache rollback procedure and release-owner checklist.","step_count":6,"url":"https:\/\/amo.ng\/workflows\/build-verify-offline-searchable-directory-pwa","public_url":"https:\/\/amo.ng\/workflows\/build-verify-offline-searchable-directory-pwa"},{"amo_id":"AMO-W-000035","title":"Implement a Retrieval-Grounded Support Triage Pilot","slug":"implement-retrieval-grounded-support-triage-pilot","summary":"Implement an approved knowledge-assistant architecture, integrate it into bounded support triage in sandbox or shadow mode, evaluate retrieval\/citation\/abstention quality, and prepare a controlled change decision.","outcome":"Repository\/configuration manifest, knowledge and entitlement boundary record, triage action matrix, synthetic\/shadow evaluation ledger, claim\/citation and failure-slice analysis, manual fallback\/disablement plan, and evidence for an Approve, Approve with conditions, Hold, or Reject decision by authorized owners.","step_count":4,"url":"https:\/\/amo.ng\/workflows\/implement-retrieval-grounded-support-triage-pilot","public_url":"https:\/\/amo.ng\/workflows\/implement-retrieval-grounded-support-triage-pilot"},{"amo_id":"AMO-W-000034","title":"Deliver a Marketing Website from Approved Brief to Release Gate","slug":"deliver-marketing-website-approved-brief-release-gate","summary":"Turn supplied offer and search evidence into an approved landing-page brief, implement that brief in an authorized repository, verify the actual change set, and prepare release and rollback controls without deploying it.","outcome":"Approved page brief, brief-to-code traceability, change manifest, test record, unresolved integration register, release checklist, monitoring\/rollback conditions, and an accountable go\/no-go handoff.","step_count":4,"url":"https:\/\/amo.ng\/workflows\/deliver-marketing-website-approved-brief-release-gate","public_url":"https:\/\/amo.ng\/workflows\/deliver-marketing-website-approved-brief-release-gate"},{"amo_id":"AMO-W-000033","title":"Implement CRM Lead Routing with n8n in Staging","slug":"implement-crm-lead-routing-n8n-staging","summary":"Reconcile current lead-routing and SLA evidence, design the n8n flow, configure CRM-side controls in sandbox, implement the n8n orchestration in staging, and verify retry\/recovery safety.","outcome":"Routing\/SLA contract, n8n blueprint, CRM and workflow configuration manifests, synthetic execution ledger, reconciliation evidence, unsafe-retry register, disabled activation proof, recovery runbook, and owner handoff.","step_count":5,"url":"https:\/\/amo.ng\/workflows\/implement-crm-lead-routing-n8n-staging","public_url":"https:\/\/amo.ng\/workflows\/implement-crm-lead-routing-n8n-staging"},{"amo_id":"AMO-W-000032","title":"Implement an Operations Dashboard and Automated KPI Reporting","slug":"implement-operations-dashboard-automated-kpi-reporting","summary":"Govern metric definitions, specify the dashboard, implement the dashboard and disabled recurring report, then reconcile both products to authoritative evidence before decision use.","outcome":"Metric contract catalogue, dashboard specification, dashboard and reporting change manifests, source-to-output traceability, reconciliation matrix, failure\/rerun tests, trust classification, decision restrictions, and release-owner handoff.","step_count":5,"url":"https:\/\/amo.ng\/workflows\/implement-operations-dashboard-automated-kpi-reporting","public_url":"https:\/\/amo.ng\/workflows\/implement-operations-dashboard-automated-kpi-reporting"},{"amo_id":"AMO-W-000031","title":"Govern University AI Adoption, Curriculum and Impact","slug":"govern-university-ai-adoption-curriculum-impact","summary":"Move from approved university AI policy through procurement, curriculum alignment, implementation oversight, and evidence-based institutional impact decisions with accountable authority at every gate.","outcome":"A governed university AI adoption package linking approved policy to role-specific practice, educational procurement, programme alignment, curriculum currency, implementation evidence, and a bounded institutional continue, change, expand, pause, or stop decision.","step_count":5,"url":"https:\/\/amo.ng\/workflows\/govern-university-ai-adoption-curriculum-impact","public_url":"https:\/\/amo.ng\/workflows\/govern-university-ai-adoption-curriculum-impact"},{"amo_id":"AMO-W-000030","title":"Run a Responsible Campus AI Hackathon","slug":"run-responsible-campus-ai-hackathon","summary":"Run a permissioned campus AI hackathon with bounded challenges, accessible facilitation, safe data and tools, controlled prototypes, accountable judging, and post-event learning evidence.","outcome":"Guide an AI club or learning institution from a bounded challenge and safe data\/tool rules through team preparation, prototype planning, evidence-based evaluation, safety review, judging and post-event learning.","step_count":8,"url":"https:\/\/amo.ng\/workflows\/run-responsible-campus-ai-hackathon","public_url":"https:\/\/amo.ng\/workflows\/run-responsible-campus-ai-hackathon"},{"amo_id":"AMO-W-000029","title":"Build and Defend an Evidence-Grounded Academic Argument","slug":"build-defend-evidence-grounded-academic-argument","summary":"Move from a bounded academic question through source triage, a pre-draft evidence ledger, learner-owned argument development, claim verification, and an assessor-owned oral defence.","outcome":"Help a university student move from an answerable question and defensible source set to a traceable argument, challenged draft, verified citations and oral defence evidence without outsourcing final authorship.","step_count":7,"url":"https:\/\/amo.ng\/workflows\/build-defend-evidence-grounded-academic-argument","public_url":"https:\/\/amo.ng\/workflows\/build-defend-evidence-grounded-academic-argument"},{"amo_id":"AMO-W-000027","title":"Design a Governed AI Support Triage Pilot","slug":"design-governed-ai-support-triage-pilot","summary":"Assess support knowledge, design bounded AI-assisted triage and human escalation, establish sensitive-data and quality controls, and define evidence-based pilot entry, exit, and expansion decisions.","outcome":"A controlled AI support triage pilot package with knowledge-readiness evidence, explicit AI authority limits, data-minimized escalation handoffs, accountable human review, privacy controls, entry and exit criteria, and keep, improve, expand, pause, stop, or retest gates. It does not authorize automatic production deployment.","step_count":7,"url":"https:\/\/amo.ng\/workflows\/design-governed-ai-support-triage-pilot","public_url":"https:\/\/amo.ng\/workflows\/design-governed-ai-support-triage-pilot"},{"amo_id":"AMO-W-000024","title":"Rebuild Confidence in an Analytics Decision","slug":"rebuild-confidence-analytics-decision","summary":"Reconstruct broken data lineage, challenge forecast assumptions and drift, and test conclusion sensitivity before relying on a consequential analytical decision.","outcome":"A decision-integrity package containing a repaired lineage boundary, affected-output and reprocessing scope, forecast assumption and drift findings, sensitivity results, residual uncertainty, and a Use, Use with limits, Recompute, or Hold decision.","step_count":3,"url":"https:\/\/amo.ng\/workflows\/rebuild-confidence-analytics-decision","public_url":"https:\/\/amo.ng\/workflows\/rebuild-confidence-analytics-decision"},{"amo_id":"AMO-W-000023","title":"Allocate an AI Investment Portfolio Under Constraints","slug":"allocate-ai-investment-portfolio-under-constraints","summary":"Compare AI initiatives using work-design evidence, reviewer burden, model-routing economics, vendor concentration, and option value to allocate constrained investment transparently.","outcome":"A portfolio allocation package containing comparable initiative evidence, work-design choices, control and routing economics, concentration exposure, dependency and option-value analysis, funding tiers, conditions, and explicit defer or stop decisions.","step_count":5,"url":"https:\/\/amo.ng\/workflows\/allocate-ai-investment-portfolio-under-constraints","public_url":"https:\/\/amo.ng\/workflows\/allocate-ai-investment-portfolio-under-constraints"}],"meta":{"page":1,"current_page":1,"per_page":20,"total":40,"last_page":2}}