Create recurring billing events from a fixed-price contract

Proposed inputs

1. Name

   Fictional terms

   Owner

   Contract owner

   Minimum scope

   Invented identifier, dates and amount

   Quality check

   Separate the executed terms from later informal requests.

2. Name

   Prior records

   Owner

   Billing owner

   Minimum scope

   Fictional identifiers and status

   Quality check

   Give every event a stable identifier and expose incomplete export coverage.

Access and setup — proposed or unknown

Proposed minimum

1. Start with a fictional contract and a manually checked reference schedule.

2. Read the linked setup requirements before enabling access.

Compatibility unknowns

1. Unknown: tenant access, actual behavior and Canadian availability.

External actions requiring approval

1. Approve access and live writes separately; qualified owners retain consequential decisions.

Why use this

1. Make the intended distribution visible before committing it.

2. Record creation does not establish invoicing or payment.

Why an agent / simpler alternative

Useful judgment

Explain unclear corrections before the owner commits.

Simpler alternative

Use an existing fixed scheduling rule when the contract and all event fields are already validated.

Unsuitable when

Authority or the underlying agreement is disputed.

Expected deliverable and review checks

Proposed artifact

Confirmed recurring billing or revenue event records.

Critical checks

1. Reconcile the total under an approved rounding rule.

2. Existing recurring events block the entire line.

3. Verify records against the confirmed preview.

Missing output evidence

No run or resulting record independently inspected.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Two invented lines: one already has recurrence; the other is eligible but has an awkward total.

Acceptance checks

1. Existing recurring events block the entire line.

2. For the eligible line, show any rounding difference.

3. Use mock records only.

Stop conditions

1. Stop if the exercise needs real data, external access or a consequential action.

Failure signals and proposed responses

1. Signal

   Two attachments disagree about what was signed

   Why it matters

   A tidy calculation could follow the wrong agreement.

   Proposed response

   Hold the disputed input for the contract owner; do not choose by file timestamp alone.

2. Signal

   The same customer name refers to two legal entities

   Why it matters

   A correct number can still be attributed to the wrong counterparty.

   Proposed response

   Ask the owner to resolve the entity using authoritative identifiers.

3. Signal

   A reviewer changes instructions mid-run

   Why it matters

   Earlier comments may cover only the old version.

   Proposed response

   Freeze the candidate, show the changed input and obtain a new owner decision.

Effort and cost — unknown

Setup work

1. Assign an accountable reviewer, choose representative counterexamples and record what would count as a failure.

Ongoing review

1. Sample uncertain results and changes in the input format. Keep reviewer corrections so the same error can be checked again.

Unknowns

1. Unknown: licensing, configuration, usage charges, elapsed effort and reliability. No savings established.

Limits

1. The intended output describes what an authorized implementation would produce; the first exercise is offline and does not establish live compatibility or success.