Complete FAC v 1 source:TA and TB texts are defined in section 1. Purpose: inquiry drafting only. Lab maximum 2 attempts; no actual attempts execute. Six input rows:
| Row | Job | Template | Permission | Prior result | Attempts |
|---|---|---|---|---|---|
| 1 | J01 | TA | Inquiry reply only / Solo respuesta consulta | Draft only / Solo borrador | 0 |
| 2 | J02 | TA | Inquiry reply only / Solo respuesta consulta | Confirmed not accepted / No aceptado confirmado | 1 |
| 3 | J03 | TA | Inquiry reply only / Solo respuesta consulta | Unknown / Desconocido | 1 |
| 4 | J04 | TA | Withdrawn / Retirado | Draft only / Solo borrador | 0 |
| 5 | J01 | TA | Inquiry reply only / Solo respuesta consulta | Draft only / Solo borrador | 0 |
| 6 | J01 | TB | Inquiry reply only / Solo respuesta consulta | Draft only / Solo borrador | 0 |
1. Define source, purpose and template
FAC is the complete source. TA draft:“Fictional inquiry received; the source must be checked before replying.” TB:“How many units are needed in this fictional case?” Neither confirms orders, payments or delivery. Permission covers inquiry-reply drafting only, not promotions or external contact.
Permission is test input, not a credential. Production authority/purpose must be verified, not inferred from sender text. J04 explicitly withdraws permission: even harmless-looking content cannot proceed. Send nothing merely to test consent.
Activity: define source, permission, purpose, template, version and execution evidence. Distinguish draft, confirmed not accepted and unknown result without attributing these to a real provider.
Worked feedback
Feedback: only local decisions are documented. TA/TB are fictional text. Confirmed not accepted means the case source explicitly rules out acceptance; unknown establishes neither success nor failure. Invent no recipient, access token or send.
2. Separate exact repetition from different work
J01 appears with TA, an exact TA copy, and then TB. The copy creates no new job;TB under the same IDis a conflict, not an authorized update. Job identity must remain tied to content/purpose, but no durable server keys are implemented here.
A key alone guarantees no cross-service deduplication. Operational systems need durable decisions and authorized-source reconciliation. This ledger exists for one test run only and connects to no mailbox. Never call a local Mapproduction storage.
Activity: compare six rows, record template/purpose/result fingerprint and identify duplicate/conflict. Separate rows from unique IDs. Preserve the source instead of deleting errors.
Worked feedback
Feedback:6 rows,4 unique IDs,1 exact duplicate,1 conflict. J01 draft ready;J02 retry plan;J03 hold for reconciliation;J04 permission blocked. None is sent or received by another person.
3. Plan retries only with evidence and explicit limits
The laboratory limit is 2 attempts/job, a case-specific rule rather than universal advice or support commitment. J02 has 1 attempt and confirmed nonacceptance: another simulated attempt may be planned if permission remains. Planning neither increments nor executes attempts.
J03 has unknown outcome. Do not classify it as definitive failure and blindly retry: a prior action may exist without confirmation. Hold and propose reconciliation. If permission is withdrawn while pending, block even when a result later appears.
Activity: separate variants VR1 clarify J03 as confirmed not accepted;VR2 sets J02 attempts 2;VR3 withdraws J02 permission. Identify exit condition and missing evidence, no timers or sends.
Worked feedback
Feedback:VR1 permits a simulated plan with valid permission and 1 attempt;VR2 requires proposed manual recovery at the limit, not resetting counters;VR3 blocks. Negative/noninteger counts are invalid, not loopholes. No variant demonstrates actual recovery.
4. Design recovery and audit without claiming execution
A recovery note records ID, version, last known result, missing evidence and proposed check. Preserve uncertainty; absence of error is not delivered. No actual service receipts or mailbox checks are supplied.
Deliver contract, six-decision table, retry/hold matrix and recovery note. Invariants: no messages sent, no inferred permission, no counter reset to bypass limits, no duplicate treated as new work. Failed invariants cannot be labeled production ready.
Activity: walk through base/VR1–VR3 plus invalid-counter and unavailable-source tests. Self-inspect source/permission, identity, recovery and limits 0–2 for editorial guidance only. Apply no free-program threshold or PRO grade.
Worked feedback
Feedback: missing source→hold; invalid count→invalid input; unknown result→reconcile. This is a local design, not active automation, completed human service or guaranteed delivery. No enrollment, statement, benefits, payments or external channels.