Object-oriented Modeling of Actions and Objects

[AdamSobieski]

I was recently working on a software architectural sketch which involves some interfaces which could be useful to those interested in automated planning and scheduling.

public interface IState
{
    // ...
}

public interface IAction
{
    bool CanInvoke(IState state);
    IState Invoke(IState state);

    bool CanUninvoke(IState state);
    IState Uninvoke(IState state);
}

public interface IObject
{
    bool CanBeInvokedUpon(IAction action, IState context);
    void InvokeUpon(IAction action, IState context);

    bool CanBeUninvokedUpon(IAction action, IState context);
    void UninvokeUpon(IAction action, IState context);
}

In addition to there being preconditions for actions in contexts (IAction::CanInvoke), as expected, some objects of actions could have preconditions for having action performed on them in contexts (IObject::CanBeInvokedUpon). This could, for instance, allow stateful objects to encapsulate custom logic for determining when actions, in contexts, could be performed on them.

Any thoughts on these interfaces?