What
Creates a visibility/entity/SEO/AEO/GEO/perception packet for almostmagic.net.au.
Manage the brand records used by your visibility reviews. Fictional examples are labelled in their descriptions.
Use Peterman itself to prepare the Almost Magic visibility packet, ingest available upstream app packets, and stage receiver packets for Concierge, Ripple, Spark, CK Writer, VISCHECK, Bada Bing, Signal Hunter, and Costanza.
Creates a visibility/entity/SEO/AEO/GEO/perception packet for almostmagic.net.au.
For the AMTL operator. digitalarmour.com.au is only the safe example customer context.
Turns visibility evidence into reviewable next actions without promising rankings or AI mentions.
Peterman checks what it knows, says what is missing, prepares packets for the other apps, and refuses to fake delivery.
Visibility can vanish before anyone notices the rankings moved.
Peterman treats every visibility claim as provisional until it has a source, a probe, an activity record, and a next action. Operators approve outputs before anything reaches a customer-facing report or read-only surface.
What Peterman is hired to do for the operator: reduce visibility-review effort, explain source support, and keep customer claims blocked until the support is strong.
Prompt probes, brand mention position, hallucination checks, competitor context, and recorded model observations.
Open chamber recordEntity clarity, source-language drift, query intent fit, and the terms machines can reliably map back to the brand.
Open chamber recordNeighbouring concepts, competitor distance, weak clusters, and source paths for why a score moved.
Open chamber recordSource quality, citation strength, SERP gaps, and provenance signals that deserve operator attention.
Open chamber recordAsk a visibility question, capture keyword/context outputs, and keep recommendations behind internal approval.
Open API endpointSource records, citations, claim checks, confidence notes, and the reason an output is ready or held back.
Open chamber recordApproved report copy, content briefs, schema suggestions, and operator-safe drafts for customer delivery.
Open chamber recordPrefer primary, current, attributable sources. Treat unattributed summaries and scraped echoes as weak evidence.
Check whether the citation proves the claim, only mentions related terms, or points to a stale/irrelevant page.
Probe multiple phrasings, compare competitor mentions, and record when a model refuses or invents details.
Every score should drill down to inputs, method, source freshness, confidence, and next operator action.
Five hundred Peterman rows are split into operator helpers, admin review controls, and approval-gated work. Each row keeps the literal prompt intent, Peterman interpretation, placement, and route-backed drilldown visible.
External AI generation has been removed. Local visibility records and existing receipts remain available for review.
Private pulse for runtime evidence, source gates, prompt evidence, report receipts, and release denial. It helps the operator choose the next review without starting external work.
Watcher rows for runtime truth, score drilldowns, prompt evidence, source gates, and release denial. These are inspectable prompts for operator attention, not crawlers or model calls.
Prompt and citation checks stay as operator review work until provider execution is separately approved. Nothing here promises mentions, rankings, recommendations, or customer-ready output.
Safe private actions for evidence inspection, source-gate review, visibility packet review, and release hold. Each row has a route-backed drilldown.
Draft-only local outbox for Signal Hunter visibility checks, operator packets, and customer-route holds. It does not send, publish, release, or create customer access.
What Peterman believes, scores, recommends, or places in a report.
Label, URL or operator note, source type, and why the source is fit to use.
Date checked, confidence, status, and whether the receipt is superseded.
Draft and review receipts stay internal. Only approved receipts can feed customer outputs.
Receipt-backed report draft for operators. It stays internal unless every supporting receipt is approved and strong.
Preview what may be allowed into an approved output while raw prompt notes, raw source traces, and customer self-service stay blocked.
Check the fields that must stay out of approved output before any customer-visible report is released.
Check the signed redaction-review shape before any approved output moves toward a customer surface.
Prepare the exact signed-review payload Mani can approve later without creating a customer surface.
Define the future approved-output route without creating customer access, customer self-service, or write actions.
Prove the reserved customer visibility route denies access until SSO, tenant boundary, redaction review, and release approval are in place.
Record the denied customer visibility route as a local audit event without writing a production audit log or capturing customer identity.
Link the route denial receipt and local audit receipt into a local chain without writing a production audit log or opening Peterman to customers.
Define the required audit fields and route events before any Peterman output can move into a production audit store or customer surface.
Workshop SSO is the approved external account path for approved read-only outputs. Peterman still stays internal-use only until provider details and a real signed-in session are proved.
Show the reserved customer route failing closed behind an identity and tenant guard while real Workshop SSO remains unproved.
Check the signed approval shape before any approved output moves toward a read-only customer surface.
Prepare the exact release-approval payload Mani can approve later without creating a customer surface.
Link the preview, redaction, read-only surface, and release approval receipts without creating customer access.
Operator-entered probe notes only. Peterman does not claim external model execution, ranking movement, or customer-safe visibility evidence from this ledger alone.
Tracked competitors and evidence coverage only. Peterman does not claim mentions, ranking, or citation comparison until prompt probes and source receipts exist.
Search works across current Peterman records and route-backed evidence. Source search is a gated knowledge path: proposed sources, approval packet, inventory, indexing or embeddings, then retrieval evidence. Peterman can accept internal and external source candidates, but it does not ingest, crawl, embed, retrieve, or run providers until Mani approves the exact include roots, exclusions, and run action.
Local folders, Dropbox-local folders, NAS paths, and approved AMTL artefacts can be proposed. They remain candidates until the source packet is signed.
URLs, public references, or vendor data can be named, but crawling, paid data, and external sends need separate approval.
Source approval and inventory gates are visible. Indexing, retrieval, provider execution, customer surfaces, and release remain blocked unless explicitly opened.
Peterman can use approved local folders, Dropbox-as-local-folder, NAS 1, NAS 2, and SummonAI Kit evidence only after Mani confirms exclusions. No indexing starts from this screen.
Use this to shape Mani's exact include/exclude decision. A valid draft can support a future indexing plan, but it still does not crawl, embed, write vectors, retrieve, or send externally.
Builds a manifest hash and source-run checklist from a valid approval draft. It does not read folders, crawl, embed, write vectors, retrieve, or send externally.
Creates a local receipt hash tied to a dry-run manifest. It records review only and still blocks inventory, indexing, vector writes, retrieval, and external sends.
Checks that the approval draft, dry-run manifest, and receipt hash line up. It is evidence only and still refuses inventory, indexing, retrieval, and external sends.
Shows the exact items still blocking a source run. Current state is blocked until Mani gives separate approval for the manifest and action.
Creates the exact operator request needed before a source inventory run. It is copy-ready evidence only and does not approve or start the run.
Checks a pasted Mani approval against the exact manifest, date, signature, and action. It records proof only and does not touch sources.
Defines the receipt a future inventory runner must produce. This card performs no folder listing, file read, indexing, or retrieval.
Local diagnostic only. Peterman cannot claim production vector runtime until a Postgres target, migration, vector write, retrieval eval, and rollback are proven.
Peterman is internal-use only. Customers may receive approved outputs or read-only surfaces, but they do not operate Peterman or see raw evidence/probe ledgers.
Peterman stays internal. The receipt separates operator work, approved customer outputs, and blocked self-service access.
Local checklist only. Peterman is not deployed, published, externally sent, migrated, or customer-visible from this packet.
Private evidence is useful, but Peterman cannot be called complete until the internal visibility engine, source quality, report release, and governance paths are proven end to end.
Latest private Peterman evidence, evidence files, and unresolved blockers in one read-only receipt. This ledger does not approve source inventory, indexing, SummonAI testing, release, or customer operation.
Peterman prepares a local visibility review with source-quality notes, citation questions, and operator-safe draft recommendations.
Drop a claim here, then link it to citations, freshness, confidence, and approval state.
Compare model answers, competitor mentions, and source behavior before recommending a move.
Use this space to explain why a score changed and how to read the receipts.