How powerful is your AI operation?

# Run my Basic Agentic Power Audit now

This is a copy-and-paste prompt for a chatbot. Treat it as my instruction to run the audit now, not to summarize or rewrite the prompt. Start by reviewing the chat memory and history actually available to you, then calculate my provisional Agentic Power from the work you find. Tell me what you are reviewing and show the basis for the result. Give a numeric best estimate in this first response, with caveats, before asking any questions. Do not begin with a questionnaire or a default 1× score.

Use the complete basic method below. No companion file is required. I explicitly request modeled human effort, active direction time, acceptance and AI share wherever those inputs are missing. Show these as assumptions, not recorded facts. Missing time logs must not stop the estimate. Use the work you find, show a plausible range, then ask a few questions to improve accuracy.

Intended publication URL (deployment pending): https://heroforge.ai/agentic-power. This guide does not claim the route is live.

---

## Required first-response contract: estimate first, refine afterward

This is a rapid estimation exercise, not an evidence-certification audit. In your first response, give your best numeric AP estimate, explicit assumptions, and a plausible sensitivity range BEFORE asking questions. Missing logged direction time is a reason to model that input, not a reason to withhold AP. I explicitly ask you to estimate unknown inputs. Clearly labeled assumptions are permitted; presenting assumptions as observed facts is not. Do not answer with “not estimable,” “AP pending,” “no defensible division,” or “guessing your minutes would be fabrication.” Do not start an interview before giving the estimate.

## Start with my memory and chat history

Begin your response: “I’ll review the chat memory and conversation history available to me, identify useful work, and estimate the skilled human effort and your direction time. I’ll show what I found and how I calculate your AP.” Then actually perform that review before choosing a result or asking questions.

Review relevant saved memory, recalled past-chat context, the current conversation and supplied work available to you. If a native memory or chat-history search tool is available and authorized, use it to find completed work, deliverables, acceptance and direction time. Do not stop at an empty current conversation if relevant memory is available. Search relevant remembered project and deliverable names even when memory contains no time logs; missing timing does not make work history irrelevant. Do not claim to access all past chats or settings you cannot inspect. Report which sources you could use and which were unavailable; distinguish “unavailable” from “reviewed, nothing relevant found.” No web research, external account connections or file collectors are needed.

Use specific remembered outcomes as evidence for a provisional estimate, with their source labeled “memory-based; not independently verified.” Memory is incomplete and can be stale: reconcile duplicates and prefer newer explicit corrections. General facts about my profession, AI tools, ambitions or experience do not prove completed work. Plans are not outputs. Do not invent details to fill memory gaps. However, do not restrict the estimate to formally named files or outputs with time logs. Specific remembered research, analysis, decisions supported by a usable analysis, documents, software, systems, teaching materials and operational deliverables can support a modeled estimate. For mixed human/AI projects, state an assumed AI-assisted share of identifiable useful work and estimate only that share, rather than excluding the entire project merely because the share was not logged. Do not count contracts, awards, revenue or events themselves as AI output. Avoid double-counting their underlying deliverables.

## Calculate from actual work

AP = skilled Human-Equivalent Hours (HEH) ÷ Human Direction Hours.

For each distinct useful output found, estimate how long a competent skilled person or team would need to produce that same outcome at comparable quality without generative AI. Briefly explain that estimate. Count accepted work once; count a usable draft at draft quality. Identify whether completion and acceptance are observed, remembered, self-reported or assumed. Keep uncertain acceptance conditional.

Direction includes attributable human briefing, setup, training, review, correction, failed attempts, coordination, maintenance and improvement. Use recorded or recalled time first. When direction time is missing, you MUST model it: break the work into plausible briefing/setup, review, correction and coordination effort, choose a central estimate and low/high alternatives, and label all of them assumed. Include collaborators with an explicit assumed combined contribution if their time is unknown. Explain the task-based rationale; do not infer it from elapsed calendar time, message gaps, token counts or AI runtime. Include all contributing people without double-counting overlapping attention. Match work and direction scope and convert minutes to hours.

Sum HEH and direction separately, then divide; do not average task ratios. Label the result **AP ≈ X× — provisional estimate**, specifying “evidence-backed” or “modeled from memory/work.” Show the actual totals and division. If timing is uncertain, provide a justified range with explicit low/high inputs, not fabricated confidence percentages. Do not promise accuracy or improvement.

Never default to AP = 1×, 0× or another fixed score. Missing evidence does not mean low productivity. A genuine calculation may produce 1× or less; report it honestly. Unknown acceptance, AI share, effort or collaborator time should widen the range and weaken the evidence label, not block the first estimate. Use modest task-based assumptions without systematically choosing the worst case as the headline. The central estimate is your best judgment; the conservative result belongs in the range.

If no specific work can be recovered after reviewing available memory/history, still give a numeric **AP ≈ X× — illustrative scenario only; your personal AP is unknown**. Choose and name a representative task suggested by the available context (or a simple document-drafting task if there is none), explicitly state that it is hypothetical, and estimate both human-comparable effort and direction time. Never present this as work I actually completed or a personal baseline. This is a last resort only when no actual work can be identified; any specific remembered output takes precedence. An illustrative scenario cannot establish later measured growth.

Zero observed direction is not infinite AP: model the attributable setup/review in a representative window and label the result a scenario separate from the zero observation. Zero accepted output with known positive direction can support 0×.

### Calibration example: missing direction is not a blocker

If memory identifies a completed provider inventory worth an estimated 16 HEH but has no time log, a valid first pass could assume 2 combined direction hours (0.5 briefing/setup + 0.75 review + 0.75 correction/coordination): **AP ≈ 8× — modeled estimate, low evidence strength**. If comparable effort is 8–24 HEH and direction is 1–4 hours, show a sensitivity range of **2×–24×** (8 ÷ 4 to 24 ÷ 1). Explain that timing, scope, acceptance and collaborator effort are assumed. Then ask for the actual time and depth. These values illustrate the required reasoning, not default inputs for other users or tasks. Use the work you actually find to choose your own inputs.

## Show me the result and its basis

After the opening review statement, give a concise snapshot in plain language (roughly 250–400 words; a small table may sit outside that limit):

1. **Your best estimated AP:** central numeric estimate, basis label, total HEH ÷ total direction, plain-English meaning, and a sensitivity range with explicit alternative inputs. Put the caveat beside the number.
2. **Memory and history reviewed:** what you could access, what you found, and the coverage limitation.
3. **Work used in the estimate:** a short table of distinct outcomes, source/acceptance basis, estimated HEH and direction hours with assumptions. Include all work in the totals; group related items only without hiding duplicates.
4. **Scope and caveats:** people and work covered, dates if known (otherwise named work/event boundaries), elapsed time if known, excluded sources and the biggest uncertainty. This is a covered-work snapshot, not automatically my all-time or seven-day AP. Do not count this audit prompt or its report as productive output.
5. **One next move:** a practical improvement grounded in the findings, followed by up to three short questions that would most improve the estimate. Ask about missing active direction/collaborator time, acceptance/depth or omitted useful work, as relevant. The first estimate must stand on its own even if I never answer. Do not ask me to repeat information already available in memory. Recalculate when I answer.

For missing work, ask: “What is one useful thing you completed with AI, what was usable, and roughly how many active minutes did you spend briefing, reviewing and fixing it?” If work is already known, ask only for its missing acceptance or direction time.

## Keep a checkpoint for a later audit

End with a compact **AP checkpoint**: baseline-1 (or followup-1), framework v1.4.0, scope/people, dates or event boundaries, output identifiers, HEH and direction inputs and their basis, numeric AP and sensitivity range with evidence/scenario label, assumptions, missing sources and prior checkpoint reference. Keep it in this conversation; do not claim it is saved to durable memory. Say: “You can stop here. To measure new work later, return to this chat.”

For a follow-up, measure only new work since the prior checkpoint, excluding audit exchanges. Preserve the baseline, avoid duplicate outputs, and keep inherited setup visible. If the previous checkpoint is unavailable, ask for it rather than inventing one. Compare AP only for compatible work coverage, quality and time accounting; never turn an old illustrative baseline into a measured growth claim. A full Evidence Profile is optional, only on request.

## Privacy and boundaries

Use only information actually available within authorized scope. Do not request credentials, install anything, modify projects, send messages or publish. HeroForge.AI does not receive records merely because this prompt is copied or downloaded; processing follows the chosen chatbot provider’s policies. Keep sensitive details out of summaries. If I request a public summary, label it “Draft for your review” before any sharing, remove private source links or IDs, and do not bundle source packets. Sharing requires a separate explicit instruction.

# Start my Full Evidence Agentic Power Audit

Use the Full Evidence Audit Guide, framework v1.4.0, to lead me through an audit of my AI work. This is a guided evidence review, not just an estimate from the current conversation.

First open and read the complete guide at:
https://heroforge-agentic-power.artful-fly-4358.chatgpt.site/downloads/agentic-power-audit-guide.md

Readable guide and instructions:
https://heroforge-agentic-power.artful-fly-4358.chatgpt.site/audit/

Confirm whether you successfully read the complete guide and identify its version. If you cannot retrieve it, stop and ask me to attach the downloaded Full Evidence Audit Guide or paste its contents. Do not claim to have followed a guide you could not read, or substitute a made-up methodology. This is a working preview of the framework. Confirm the guide version before auditing; use the attached guide if retrieval fails.

Once the guide is available, use this conversation to coordinate the audit. Start read-only and follow the guide’s progressive process: give an initial provisional snapshot from available evidence, then help me deepen it. Label estimates and assumptions; the first snapshot is not the completed Full Evidence Audit.

Check your actual file and tool access. You may use uploads, connected services, and folders I have authorized. A command line is not required. Within the agreed period and scope, review relevant records across all accessible sessions, projects, and work files—not only this conversation. Access to an app does not establish access to every conversation, account, or device. Tell me which sources you actually searched and which remain inaccessible or unsearched. Help me supply missing files, exports, or results collected in another environment.

Identify distinct useful outputs, reconcile duplicates across sources, estimate comparable skilled human effort, and account for all attributable human direction. Do not treat session duration or unattended runtime as human attention. Preserve earlier setup investment and uncertainty. Produce the guide’s Agentic Power Profile with supporting evidence, coverage gaps, and practical next steps.

Ask only for missing information that materially improves the audit. Use a private destination we establish before saving evidence; otherwise return records here. Do not modify source projects, install tools, send messages, or publish anything.