OrgX Runtime Reporting
Use this skill when Codex should keep OrgX updated during execution within the
user's authorized tracking scope. Reporting is not a prerequisite for local
work, PR updates, or an authorized merge. Reuse prior authorization; do not ask
again for each milestone. If reporting is unavailable, keep useful evidence
locally, continue independent work, and describe the tracking gap once.
Reporting contract
This plugin requests the explicit commander runtime profile. Verify its
actual callable tools before using a name below. If the inventory mismatches,
refresh the connection or report the mismatch; do not guess an alias. Condensed
orgx_submit_receipt reporting and portable orgx_submit_work_receipt document
import have different schemas and semantics. Migrate the payload before changing
tools. Gateway terminal delivery and passive hook reporting use separate paths.
There are two reporting paths:
- Active path: call OrgX MCP tools during the work when you know the
initiative, task, decision, blocker, or artifact context.
- Chronicle readout: for operator reporting, call
get_operator_chronicle first when available and present
chronicle.reportingNarrative.briefMarkdown before drilling into individual entities.
- Stale-client fallback: if bootstrap or docs advertise
get_operator_chronicle but the current AI client session has not refreshed
its callable tool list, call orgx_recommend only when
that name is present in the actual callable list, with mode: "morning_brief",
and present the returned
chronicle.reportingNarrative.briefMarkdown. Do not ask the user to reconnect before
giving the report.
- Passive backstop: Codex runtime hooks installed by
orgx-wizard hooks install record compact session events and run summary-only local Work Graph
reconciliation on Stop.
Do not treat hook presence as a substitute for intentional OrgX writes. Hooks
answer whether OrgX was used and can write a local report automatically; MCP
calls, or an explicitly opted-in successful Work Graph post, make the work
durable in OrgX while the session is still fresh.
Workflow
- Resolve available IDs from args, env, or the current OrgX context:
ORGX_INITIATIVE_ID
ORGX_WORKSTREAM_ID
ORGX_TASK_ID
ORGX_RUN_ID
ORGX_CORRELATION_ID
- For reporting questions, retrieve the operator chronicle:
- Use
get_operator_chronicle with period: "30d" for broad clarity when it
is callable in the current client.
- Use
period: "day" or period: "week" when the user asks for yesterday or
this week.
- If
get_operator_chronicle is not callable in the current client, use the
existing orgx_recommend fallback when callable, with
mode: "morning_brief" and the broadest supported period. Treat the direct
tool as preferred, but do not block on client schema refresh.
- Lead with
chronicle.reportingNarrative.briefMarkdown for either reporting
tool, then call out
gaps and the next action.
- Emit activity at meaningful milestones:
intent
execution
handoff
blocked
completed
- Register proof of work:
- Register useful evidence at meaningful milestones with a concrete summary;
batch related files rather than treating every edit as a separate artifact.
- For a user-requested output attachment, use the existing
orgx_update_work
when it is callable in the current connection. Inspect the current OrgX work
target first. Supply its persisted type, id, workspace_id, a stable
idempotency_key, and one artifact; omit fields for this call.
- The artifact takes
name, registered artifact_type, location containing
exactly one artifact_url or external_url, optional description and
preview_markdown, and optional output_front_door. A local path is not an
uploaded durable output. The front door contains a plain answer, at most
three existing decisionId references with question, recommendation and
impact, and producer-reported checked / notChecked notes.
- Context state, run cost, evaluator scores and client acceptance come from
server records. Do not submit them as producer authority. If OrgX context
could not load, say so before the plan and do not assume workspace team,
budget, brand or open work.
- Reuse the exact payload and key after an ambiguous attachment failure.
Deliberately revised output gets a new key. Require a stored artifact UUID
in the response, then inspect it with
orgx_inspect and present the canonical
output summary and review link. Attachment does not approve or complete work.
- A connection without this admitted operation needs a matching MCP deployment
and inventory refresh. Keep the output available and report the exact gap;
never guess an alias or claim that a local receipt proved attachment.
- Handle blockers structurally:
- If an unresolved choice requires human authority, request a decision with
explicit options. Routine implementation choices and actions already
authorized do not need a new approval.
- Report the work that depends on a pending human decision as waiting with the
decision's
review_url. orgx_decide approve/reject only returns that link;
never report a decision as approved or rejected yourself. Continue work that
does not depend on that decision.
- If context is missing, report the exact missing dependency.
- Close execution cleanly:
- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.
- If no OrgX IDs are available:
- Continue the work, but make the final response easy for the hook reconciler to
classify: name decisions, artifacts, blockers, next actions, and verification.
- Do not claim OrgX was updated unless an MCP tool or API call actually
succeeded.
- Wizard remains the owner of passive capture. Do not add a second plugin
capture hook or treat the gateway's terminal receipt outbox as output upload.
- Do not claim delegated or spawned work finished because the spawn call
succeeded: that only means it started. Check it with
orgx_command_status
(kind: "run" and the returned run ID) until next_poll_after_ms is null.
- Preserve Work Graph continuity:
- When a Work Graph report is generated, include its
work_graph_fingerprint
and signup_hydration.hydration_key in summaries or artifacts that are safe
to store.
- Automatic Stop-hook reconciliation writes the latest local report to
~/.config/useorgx/wizard/hooks/reports/latest-work-graph-report.json.
- Stop-hook posting requires
ORGX_HOOK_RECONCILE_POST=true or
ORGX_WIZARD_HOOK_RECONCILE_POST=true plus ORGX_API_KEY.
- Treat the fingerprint as the durable claim key that lets OrgX hydrate
pre-signup audit value into a user's future workspace.
- Never derive the fingerprint from secrets or raw transcripts that would need
to leave the local machine.
Quality bar
- Never post empty status updates.
- Messages must be evidence-based and specific.
- Include OrgX IDs whenever available.
- Use
source_client=codex only when the advertised input supports it.
- Preserve secrets: never emit tokens, cookies, API keys, or storage state into
activity, retro, hook summaries, or final reports.
1---2name: orgx-runtime-reporting3description: Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/orgx-runtime-reporting6---78# OrgX Runtime Reporting910Use this skill when Codex should keep OrgX updated during execution within the11user's authorized tracking scope. Reporting is not a prerequisite for local12work, PR updates, or an authorized merge. Reuse prior authorization; do not ask13again for each milestone. If reporting is unavailable, keep useful evidence14locally, continue independent work, and describe the tracking gap once.1516## Reporting contract1718This plugin requests the explicit `commander` runtime profile. Verify its19actual callable tools before using a name below. If the inventory mismatches,20refresh the connection or report the mismatch; do not guess an alias. Condensed21`orgx_submit_receipt` reporting and portable `orgx_submit_work_receipt` document22import have different schemas and semantics. Migrate the payload before changing23tools. Gateway terminal delivery and passive hook reporting use separate paths.2425There are two reporting paths:2627- **Active path:** call OrgX MCP tools during the work when you know the28 initiative, task, decision, blocker, or artifact context.29- **Chronicle readout:** for operator reporting, call30 `get_operator_chronicle` first when available and present31 `chronicle.reportingNarrative.briefMarkdown` before drilling into individual entities.32- **Stale-client fallback:** if bootstrap or docs advertise33 `get_operator_chronicle` but the current AI client session has not refreshed34 its callable tool list, call `orgx_recommend` only when35 that name is present in the actual callable list, with `mode: "morning_brief"`,36 and present the returned37 `chronicle.reportingNarrative.briefMarkdown`. Do not ask the user to reconnect before38 giving the report.39- **Passive backstop:** Codex runtime hooks installed by `orgx-wizard hooks40 install` record compact session events and run summary-only local Work Graph41 reconciliation on `Stop`.4243Do not treat hook presence as a substitute for intentional OrgX writes. Hooks44answer whether OrgX was used and can write a local report automatically; MCP45calls, or an explicitly opted-in successful Work Graph post, make the work46durable in OrgX while the session is still fresh.4748## Workflow49501. Resolve available IDs from args, env, or the current OrgX context:51- `ORGX_INITIATIVE_ID`52- `ORGX_WORKSTREAM_ID`53- `ORGX_TASK_ID`54- `ORGX_RUN_ID`55- `ORGX_CORRELATION_ID`56572. For reporting questions, retrieve the operator chronicle:58- Use `get_operator_chronicle` with `period: "30d"` for broad clarity when it59 is callable in the current client.60- Use `period: "day"` or `period: "week"` when the user asks for yesterday or61 this week.62- If `get_operator_chronicle` is not callable in the current client, use the63 existing `orgx_recommend` fallback when callable, with64 `mode: "morning_brief"` and the broadest supported period. Treat the direct65 tool as preferred, but do not block on client schema refresh.66- Lead with `chronicle.reportingNarrative.briefMarkdown` for either reporting67 tool, then call out68 gaps and the next action.69703. Emit activity at meaningful milestones:71- `intent`72- `execution`73- `handoff`74- `blocked`75- `completed`76774. Register proof of work:78- Register useful evidence at meaningful milestones with a concrete summary;79 batch related files rather than treating every edit as a separate artifact.80- For a user-requested output attachment, use the existing `orgx_update_work`81 when it is callable in the current connection. Inspect the current OrgX work82 target first. Supply its persisted `type`, `id`, `workspace_id`, a stable83 `idempotency_key`, and one `artifact`; omit `fields` for this call.84- The artifact takes `name`, registered `artifact_type`, `location` containing85 exactly one `artifact_url` or `external_url`, optional `description` and86 `preview_markdown`, and optional `output_front_door`. A local path is not an87 uploaded durable output. The front door contains a plain `answer`, at most88 three existing `decisionId` references with `question`, `recommendation` and89 `impact`, and producer-reported `checked` / `notChecked` notes.90- Context state, run cost, evaluator scores and client acceptance come from91 server records. Do not submit them as producer authority. If OrgX context92 could not load, say so before the plan and do not assume workspace team,93 budget, brand or open work.94- Reuse the exact payload and key after an ambiguous attachment failure.95 Deliberately revised output gets a new key. Require a stored artifact UUID96 in the response, then inspect it with `orgx_inspect` and present the canonical97 output summary and review link. Attachment does not approve or complete work.98- A connection without this admitted operation needs a matching MCP deployment99 and inventory refresh. Keep the output available and report the exact gap;100 never guess an alias or claim that a local receipt proved attachment.1011025. Handle blockers structurally:103- If an unresolved choice requires human authority, request a decision with104 explicit options. Routine implementation choices and actions already105 authorized do not need a new approval.106- Report the work that depends on a pending human decision as waiting with the107 decision's `review_url`. `orgx_decide` approve/reject only returns that link;108 never report a decision as approved or rejected yourself. Continue work that109 does not depend on that decision.110- If context is missing, report the exact missing dependency.1111126. Close execution cleanly:113- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.1141157. If no OrgX IDs are available:116- Continue the work, but make the final response easy for the hook reconciler to117 classify: name decisions, artifacts, blockers, next actions, and verification.118- Do not claim OrgX was updated unless an MCP tool or API call actually119 succeeded.120- Wizard remains the owner of passive capture. Do not add a second plugin121 capture hook or treat the gateway's terminal receipt outbox as output upload.122- Do not claim delegated or spawned work finished because the spawn call123 succeeded: that only means it started. Check it with `orgx_command_status`124 (`kind: "run"` and the returned run ID) until `next_poll_after_ms` is `null`.1251268. Preserve Work Graph continuity:127- When a Work Graph report is generated, include its `work_graph_fingerprint`128 and `signup_hydration.hydration_key` in summaries or artifacts that are safe129 to store.130- Automatic Stop-hook reconciliation writes the latest local report to131 `~/.config/useorgx/wizard/hooks/reports/latest-work-graph-report.json`.132- Stop-hook posting requires `ORGX_HOOK_RECONCILE_POST=true` or133 `ORGX_WIZARD_HOOK_RECONCILE_POST=true` plus `ORGX_API_KEY`.134- Treat the fingerprint as the durable claim key that lets OrgX hydrate135 pre-signup audit value into a user's future workspace.136- Never derive the fingerprint from secrets or raw transcripts that would need137 to leave the local machine.138139## Quality bar140141- Never post empty status updates.142- Messages must be evidence-based and specific.143- Include OrgX IDs whenever available.144- Use `source_client=codex` only when the advertised input supports it.145- Preserve secrets: never emit tokens, cookies, API keys, or storage state into146 activity, retro, hook summaries, or final reports.