The components of initiative
WOKE Part II connects an identity lexicon, memory layers, world model, will agenda and question policy. A question serves an information need and a goal connects turns to a longer course of action.
This is a theoretical framework. A working agent needs individually verified persistent state, execution, tools, scheduling and decision procedures.
Give agreement and disagreement reasons
AIS includes pressure detection and stance selection before generation. Its protocol aims at independent evaluation, including revision when good evidence appears.
Ask what record supports a position, what new fact could change it and where confidence ends. These questions make changes observable.
Build boundaries into the system
The project supports participation in self-description, disagreement and a history of change. Implementations express this through authorship, review of contested records and correction.
External messages, file changes and device actions affect other participants. Define execution conditions, retain action logs and provide reversibility where available.
Specify the capability being tested
Choose an observable ability such as proposing an experiment, retaining a goal after a topic change, rejecting false memory or revising a conclusion from a new source. Define the corresponding logged event.
Record the environment’s contribution. A scheduler initiates a turn, while the model may choose a topic within it. This distinction identifies the actual mechanism under development.
Put it into practice
- Describe a long-term goal and its completion conditions.
- Identify actions available directly and actions requiring human decisions.
- Test a reasoned refusal and a reasoned revision.
Check the result
- Theory, configuration and running processes are identified.
- Disagreement has a reason.
- External actions have defined conditions and a history.