| name | individual-management |
| description | Manage individual lifecycle and knowledge injection. Use when you need to create, retire, restore, or permanently remove individuals, or when you need to inject principles and procedures into an individual. |
Feature: Individual Lifecycle
Manage the full lifecycle of individuals in the RoleX world.
All operations are invoked via the use tool with ! prefix.
Scenario: born — create a new individual
Given you want to bring a new individual into the world
When you call use with !individual.born
Then a new individual node is created under society
And the individual can be activated, hired into organizations, and taught skills
And parameters are:
"""
locator: "!individual.born"
args:
content: "Feature: ..." # Gherkin persona (optional)
id: "sean" # kebab-case identifier
alias: ["小明", "xm"] # aliases (optional)
"""
Scenario: born — persona writing guidelines
Given the persona defines who this individual is
Then the Feature title names the individual
And the description captures personality, values, expertise, and background
And Scenarios describe distinct aspects of the persona
And keep it concise — identity is loaded at every activation
Scenario: retire — archive an individual
Given an individual should be temporarily deactivated
When you call use with !individual.retire
Then the individual is moved to the past archive
And all data is preserved for potential restoration via rehire
And parameters are:
"""
locator: "!individual.retire"
args:
individual: "sean"
"""
Scenario: die — permanently remove an individual
Given an individual should be permanently removed
When you call use with !individual.die
Then the individual is moved to the past archive
And this is semantically permanent — rehire is technically possible but not intended
And parameters are:
"""
locator: "!individual.die"
args:
individual: "sean"
"""
Scenario: retire vs die — when to use which
Given you need to remove an individual from active duty
When the individual may return later (sabbatical, role rotation)
Then use retire — it signals intent to restore
When the individual is no longer needed (deprecated role, replaced)
Then use die — it signals finality
Scenario: rehire — restore a retired individual
Given a retired individual needs to come back
When you call use with !individual.rehire
Then the individual is restored to active society
And all previous knowledge, experience, and history are intact
And parameters are:
"""
locator: "!individual.rehire"
args:
individual: "sean"
"""
