SERVICE TERMS
Use PostSteward only for authority and content you are permitted to publish.
These terms describe the product boundary while PostSteward is moving through restricted release gates. Provider terms, API access and charges remain separate.
Your authority and content
You are responsible for ensuring that you have the right to connect each social account, source repository and payment method, and that the content you approve may lawfully be published to the selected destination. An agent grant does not create rights you do not already have.
Do not use PostSteward to bypass provider restrictions, abuse access controls, impersonate another account owner, send credentials as content or intentionally create duplicate external effects.
External providers
Social platforms, identity providers, Stripe, GitHub and Cloudflare are independent services. Their availability, rate limits, approval requirements, billing and policies are outside PostSteward's direct control. A provider can reject, delay, remove or change access to content or APIs after PostSteward has acted.
PostSteward distinguishes reservations, provider creation evidence, independent readback and ambiguous effects. A network response alone is not a promise of exactly-once behaviour inside an external provider.
Free and Advanced
Direct reviewed publishing and explicit scheduling are part of the Free service contract. Advanced is priced at USD 5 per workspace per month when the deployment and rollout policy enable it. Advanced adds bounded continuing operation around reviewed sources. Payment alone does not expand provider authority, agent scopes or automatically enable an automation profile.
Provider API or developer-program charges are not included in the PostSteward service price. Optional settlement methods such as MPP are separate capabilities and may be disabled.
Safety controls
PostSteward may pause, fence, quarantine or refuse an operation when authority, identity, idempotency, billing, recovery state or external-effect evidence is uncertain. Those fail-closed behaviours are part of the service design and can temporarily prevent publication even when the underlying provider is reachable.
Cancellation, account disconnect, token revocation and recovery quarantine block future unclaimed work. They cannot guarantee reversal of an external provider effect that already started.
Release availability
Features can exist in source code before they are enabled or externally accepted in a deployed environment. The live runtime, /help.json, /readiness.json and the reviewed release-gate ledger are authoritative for current availability. Public signup may remain restricted while technical production work continues.
Changes and support
PostSteward may evolve its limits, interfaces and release gates as the product moves toward public availability. Consequential operation contracts are versioned and tested to avoid silent authority expansion. For current product questions or a failure reference, follow the support guidance.