Security Answer Evidence Expiry Map
Check dates in your answer library and policy review dates against the allowed periods.
Security questionnaire evidence
See what changed in your approved draft and submission file.
A downloadable skill for your AI agent.
Unreviewed changes.
Source references, missing information, and questions to review stay with the findings.
Open your download and follow the start guide. Use an AI agent that can load skill files and run the included tools.
Approved draft and submission file. Confirm the case and period you want to check.
Copy the request below into your agent. Add the files and any task details it needs.
Check the findings against the original records. Choose where to save the report and follow up on open questions.
Use the Security Final Answer Approval Diff skill. Review the attached records: approved draft and submission file. Prepare this result: unreviewed changes. Include a source reference for each finding. List missing information and questions that need my review. Ask me to confirm the scope and where to save the report before you start.
It compares the earlier and later records. It separates added, removed, and changed items and keeps a reference to each source.
Approved draft and submission file.
For this task, keep one review row for each answer field + submission revision. Record approved answer, final answer, and changed scope. Keep the source location beside each value.
Link each answer to current approved evidence and its scope. Distinguish implemented controls, exceptions, planned work, and customer promises.
Do not upgrade a qualified answer to an unconditional claim. Test fixtures must be marked synthetic and kept apart from customer evidence.
A change can be intentional. The engine does not determine approval, business impact, or which version should be used.
This synthetic example shows the included check in use. Your agent uses its findings to complete your task report.
Synthetic example records
| Starting record | approved answer: source-A |
|---|---|
| Record to check | approved answer: source-B |
A difference needs review
This result comes from the checking tool in your download.
These are synthetic records from the bundled example.
{"id": "e1", "key": "answer field + submission revision / SYNTHETIC-001", "value": {"approved answer": "source-A"}}{"id": "o1", "key": "answer field + submission revision / SYNTHETIC-001", "value": {"approved answer": "source-B"}}After purchase, extract the ZIP. Run these commands from the skill folder. Use a new output folder.
python3 scripts/checks.py
python3 scripts/audit.py assets/example.json \
--files-root assets/sample-files --output-dir example-result
Expected exit code: 1. Code 0 means no helper finding. Code 1 means a finding or review item. Code 2 means incomplete or invalid input.
The check uses the records you supply. Review each finding against the original documents.
Ask your agent to save the completed task report in a folder you choose. The report template includes the result, source references, missing information, and next actions.
Tonotes does not receive your work documents through this website. Documents you share with an AI service follow that service's storage settings.
US$11 includes one skill in a ZIP with 18 files. You receive the instructions and tools to run the task with your own records.
Use an agent that supports SKILL.md instructions and Python 3.10 or later with SQLite. Your AI-agent service is separate.
Start with approved draft and submission file. Confirm the case, period, and source versions before the review.
Use customer, question, control, answer version, evidence scope to keep records distinct. The agent records the original value, an exact quote, and the source location.
Compare the baseline with the later version using exact keys. Run the Python helper on the structured records. Check each finding against its source.
Prepare the task result: unreviewed changes. Include missing evidence, unresolved questions, and the next action for each open item.
Eight synthetic cases check the tool locally. Live-agent accuracy on real documents has not been tested.