Informational draft. Not a published website. These pages have no prices and cannot take a payment, a booking, or a message.
Teaching drafts
Learn
Short notes for any business, in everyday language. They are teaching drafts: a way to understand the idea, not proof that a setup has been run, and not customer proof.
- Teaching draft
Roles and setup
Define each assistant's purpose, inputs, outputs and limits, and make human decision ownership clear.
- Teaching draft
Approval boundaries
Keep drafts, exact permissions and completed actions separate. A declined or changed request must stop for review.
- Teaching draft
Handovers
Record scope, version, sources, unknowns and the next responsible role. Preparing a packet is not proof it was received.
- Teaching draft
Scheduling and monitoring
Distinguish a requested review, a saved configuration, observed execution and confirmed receipt.
- Teaching draft
Mistakes and fixes
Preserve the original decision, the proposed remedy, the approval and the verification as separate records.
- Teaching draft
Evidence and a roadmap
Show what is documented, what is untested and what should be built next.
- Teaching draft
Account readiness
Separate account existence, browser sign-in, tool connection, profile readiness and actual scheduling execution. Connection is not authority to act.