Disciplines · Compliance

Policy Bundle Card — iris-personal-coordination-standard v1.0.0

bounded agent_to_agent_contract coordination.

8sections2 minread
Markdown source
On this page

artifact_kind: policy-bundle-card artifact_name: iris-personal-coordination-standard version: 1.0.0 owner: Iris · concordia-assistant team last_reviewed: 2026-07-15 next_review: 2026-10-13 domain: iris related_phase_179_tasks: [179.6.2, 179.7.6.1, 179.10.8]#

1. Identity#

  • Domain: low-stakes personal and team coordination.
  • Use-case classes: low_stakes_personal, creative_collaboration, and bounded agent_to_agent_contract coordination.
  • Operational mode: brainstorming or mediation_support; never arbitration or legal drafting.

2. Contents#

  • Templates: shared-plan tasks, calendar windows, household responsibilities, team allocation, creator commitments, deadlines, deliverables, review points, and opt-out/renegotiation terms produced by conversation-to-agreement.ts and the Concordia agreement DSL.
  • Constraints: active private-intake and synthesis consent; party-isolated contexts; explicit assignee and temporal bounds; no inferred acceptance; no rights waiver, penalty, exclusivity, or binding financial execution.
  • Mandatory review: abuse, coercion, crisis, custody, employment rights, medical care, criminal allegations, minors, regulated finance, or very-high stakes route out through unsuitable-for-ai.ts and safety-routing.ts.
  • Jurisdiction: jurisdiction-neutral coordination only. Any legal effect requires a separate qualified-review bundle.

3. Sources#

Drafted by Iris product safety and Concordia mediation owners. The posture is grounded in UNCITRAL party-control principles, NIST AI RMF controls, and the ODR and mediation-ethics sources in mediation-negotiation-2026.md.

4. Evaluation#

Contract tests cover isolated prompts, consent revocation, safety routing, conversation-to-agreement conversion, and multi-device synthesis. Pilot value must be measured through agreement completion/cycle time and the subjective value dimensions; safety routing and private-context leakage are guardrails.

5. Use#

CONCORDIA_ARCHETYPE_CONFIG selects eligible scenarios; the Iris safety pipeline runs before intake or generation, and every emitted clause passes the Concordia static validator. Consumers are Iris intake, co-mediator mode, candidate generation, and draft review.

6. Refresh#

Refresh on safety taxonomy, consent flow, assistant model, or hard-boundary changes. Last refresh: 2026-07-15.

7. References#

  • libs/iris/concordia-assistant/src/concordia-archetype.ts
  • libs/iris/concordia-assistant/src/party-isolated-context.ts
  • libs/iris/concordia-assistant/src/safety-pipeline.ts
  • libs/iris/concordia-assistant/src/conversation-to-agreement.ts