Give agents a runtime built for marketing
The harness connects Maris to brand context, marketing tools, and your permission policy. It carries a task through tool execution and the decisions that require your input, keeping the agent’s work attached to the operating system.
Work with Maris
Give each run an identifiable working context
A Maris run has a working scope, a model route, and an admitted set of tools. The context manifest records the prompt and context bindings used by that run.
That structure matters when an agent changes real work. The task needs a known brand and target, and the operation needs a record that connects it to the run that requested it.
Keep permission and execution in the same path
Tools carry a defined permission class. Your policy determines whether Maris can proceed, must ask, or must stop. When approval is required, the proposed action becomes a decision you can inspect.
A pause preserves the task’s state. Resume continues through the runtime’s admission and execution boundaries, so approval remains connected to the operation it covers.
Give continuing work a durable execution system
Some work belongs to a schedule or a publication event. Waves records that work as due tasks, with execution attempts and outcomes. Publication follow-up and first-day performance capture use this background system.
The harness coordinates agent work; Waves carries the scheduled and event-driven follow-up. Together, they give marketing operations a lifecycle beyond a single chat response.
Explore Waves