interaction-contract

Interaction contract

Purpose

Use this skill to configure one owner reminder independently from the silent system heartbeat. This is agent runtime configuration, not part of the company model.

When to use

Use this skill:

• during Block C of first-session onboarding;
• when the owner says "let's do weekly", "come every morning", or similar;
• when a workspace is missing INTERACTION_CONTRACT.md;
• after a host migration that requires cron jobs to be recreated.

Do not use propose-change for this. The interaction contract lives in the private agent workspace and changes by explicit owner instruction.

Controls

The two controls never substitute for each other:

• the 2h heartbeat silently refreshes system health and has no delivery target;
• one declaration-keyed cron reminds the owner only on the confirmed schedule.

Recommend a daily reminder at 09:00 in the owner's IANA timezone, in the owner-controlled Telegram DM, with a 22:00-09:00 quiet window. Weekly or another cadence is valid when the owner chooses it.

Procedure

1. Keep the explicit per-agent 2h heartbeat unchanged.
2. Read owner_reminder.setup_status from agent-state/managed-scheduling.json. In an owner-controlled interactive turn, needs-owner-question means this resident agent records one human_request with kind=setup, changes the status to awaiting-owner, and asks one question for cadence/time, IANA timezone, channel, quiet window, and language. Include one recommended complete answer and its consequence. Do not ask from heartbeat or another scheduled run, and do not repeat the question while the status is awaiting-owner or deferred.
3. Accept the profile only from an owner-controlled channel. Correlate an exact reply before changing runtime state.
4. Update agent-state/managed-scheduling.json and the human-readable INTERACTION_CONTRACT.md, set setup_status=configured, and clear requires_owner_confirmation. Store the confirmation message reference and timestamp, not the reply body.
5. The resident agent itself converges the one declaration-keyed OpenClaw command cron using its host scheduling tool and adapters/openclaw/SCHEDULING.md. The package installer or host operator does not create this owner-specific job while that tool is available.
6. Verify the actual cron and run one empty/non-empty reminder smoke.
7. Reply with one mirror line.