pharaoh-finding-record

Audit finding deduplication during concurrent runs is handled by constructing a deterministic papyrus_id using the FACT_<category>_<subject_id> scheme, ensuring the same category and subject_id tuple never creates duplicate records and returning an action status of wrote or duplicate instead.

Deterministic ID traceability for audit reporting is the process of generating fixed papyrus_id keys from the finding category and subject_id to guarantee idempotency. This prevents conflicting records when multiple concurrent audit subagents attempt to write identical findings to Papyrus.

To record audit findings in Papyrus without duplicates, invoke this Skill from any audit subagent with the required category, subject_id, finding_text, and reporter_id inputs. It validates the data and writes a single entry per deterministic key, returning the papyrus_id.

Yes, you can use this deduplication approach for any audit subagent because the Skill is standalone and reusable, callable by any subagent needing to report issues into the shared Papyrus workspace without modifying existing artefacts.

Concurrent audit agents create duplicate records when they lack a deterministic papyrus_id scheme. Applying the FACT_<category>_<subject_id> key ensures only a single write per tuple across concurrent writers, reporting subsequent attempts as duplicates to prevent conflicting records.