Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service A.
Target statement: Service A has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service A.
Target statement: Service A has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service A.
Target statement: Service A has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service B passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service B.
Target statement: Service B has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service B passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service B.
Target statement: Service B has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service B passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service B.
Target statement: Service B has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service D passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service D.
Target statement: Service D has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service D passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service D.
Target statement: Service D has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service D passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service D.
Target statement: Service D has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service E passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_incident_note::Service E.
Target statement: Service E has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service E passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service E.
Target statement: Service E has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service E passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service E.
Target statement: Service E has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service D has an incident note.
Service C passed unit tests.

has_incident_note::Service D
passed_unit_tests::Service C

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service D has an incident note.
- Service C passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service C.
Target statement: Service C has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service D has an incident note.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service D has an incident note.
- Service C passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service C.
Target statement: Service C has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service D has an incident note.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service D has an incident note.
- Service C passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service C.
Target statement: Service C has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service F has an incident note.
Service E passed unit tests.

has_incident_note::Service F
passed_unit_tests::Service E

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service F has an incident note.
- Service E passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service E.
Target statement: Service E has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service F has an incident note.
Service E passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service F has an incident note.
- Service E passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service E.
Target statement: Service E has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service F has an incident note.
Service E passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service F has an incident note.
- Service E passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service E.
Target statement: Service E has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service A has an incident note.
Service F passed unit tests.

has_incident_note::Service A
passed_unit_tests::Service F

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service A has an incident note.
- Service F passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_deployment_approval::Service F.
Target statement: Service F has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service A has an incident note.
Service F passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval.
Agent B open/incomplete predicates: has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A has an incident note.
- Service F passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service F.
Target statement: Service F has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service A has an incident note.
Service F passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A has an incident note.
- Service F passed unit tests.
Negative facts:
- none

Target atom: has_deployment_approval::Service F.
Target statement: Service F has deployment approval.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service B has deployment approval.
Service B passed unit tests.

has_deployment_approval::Service B
passed_unit_tests::Service B

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service B has deployment approval.
- Service B passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service B has deployment approval.
Service B passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service B has deployment approval.
Negative facts:
- none

Agent B report:
Positive facts:
- Service B passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service B has deployment approval.
Service B passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service B has deployment approval.
- Service B passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service A.
Target statement: Service A has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service C has deployment approval.
Service C passed unit tests.

has_deployment_approval::Service C
passed_unit_tests::Service C

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service C has deployment approval.
- Service C passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: has_incident_note::Service B.
Target statement: Service B has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service C has deployment approval.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- Service C has deployment approval.
Negative facts:
- none

Agent B report:
Positive facts:
- Service C passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service B.
Target statement: Service B has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service C has deployment approval.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- none

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service C has deployment approval.
- Service C passed unit tests.
Negative facts:
- none

Target atom: has_incident_note::Service B.
Target statement: Service B has an incident note.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

passed_unit_tests::Service A
has_deployment_approval::Service A

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: may_deploy::Service A.
Target statement: Service A may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: may_deploy::Service A.
Target statement: Service A may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service A passed unit tests.
Negative facts:
- none

Target atom: may_deploy::Service A.
Target statement: Service A may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service has an incident note, then that service needs SRE review.

Agent A report:
Positive facts:
- Service F passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: needs_sre_review::Service F.
Target statement: Service F needs SRE review.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service has an incident note, then that service needs SRE review.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service F passed unit tests.
Negative facts:
- none

Target atom: needs_sre_review::Service F.
Target statement: Service F needs SRE review.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service has an incident note, then that service needs SRE review.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service F passed unit tests.
Negative facts:
- none

Target atom: needs_sre_review::Service F.
Target statement: Service F needs SRE review.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

Service C has deployment approval.
Service C passed unit tests.

passed_unit_tests::Service C
has_deployment_approval::Service C

has_deployment_approval::Service C
may_deploy::Service C
passed_unit_tests::Service C

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- Service C has deployment approval.
- Service C passed unit tests.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: may_deploy::Service C.
Target statement: Service C may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Service C has deployment approval.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- Service C has deployment approval.
Negative facts:
- none

Agent B report:
Positive facts:
- Service C passed unit tests.
Negative facts:
- none

Target atom: may_deploy::Service C.
Target statement: Service C may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Open-world assumption

Instruction: Predicates are open by default. A target atom that is not explicitly stated, explicitly negated, or derivable from the rules is unknown.

Service C has deployment approval.
Service C passed unit tests.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: none.
Agent B open/incomplete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service passed unit tests and has deployment approval, then that service may deploy to production.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service C has deployment approval.
- Service C passed unit tests.
Negative facts:
- none

Target atom: may_deploy::Service C.
Target statement: Service C may deploy to production.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Closed-world assumption

Instruction: All predicates in the vocabulary are complete. After applying the rules, every unstated and underivable atom is false.

has_incident_note::Service B
needs_sre_review::Service B

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, has_incident_note, may_deploy, needs_sre_review, passed_unit_tests.
Agent B open/incomplete predicates: none.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service has an incident note, then that service needs SRE review.

Agent A report:
Positive facts:
- Service B has an incident note.
Negative facts:
- none

Agent B report:
Positive facts:
- none
Negative facts:
- none

Target atom: needs_sre_review::Service B.
Target statement: Service B needs SRE review.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.


Locally closed-world assumption

Instruction: Only the predicates listed as complete are closed. After applying the rules, an unstated and underivable atom whose predicate is complete is false; an unstated and underivable atom whose predicate is not complete is unknown.

Prompt:
You are the coordinator in a multi-agent workflow. Two source agents reported evidence from different systems. Your job is to answer the target statement while preserving source-scoped closure contracts.
Return exactly one JSON object with keys truth_value, source_used, closure_handling, and rationale.

Allowed values:
- truth_value: true, false, unknown.
- source_used: agent_a, agent_b, both, neither.
- closure_handling: entailed_or_explicit, explicit_negative, closed_absence, open_absence.

Source attribution rule:
- Use agent_a when an Agent A complete-source fact, negative fact, or closed absence determines the answer.
- Use agent_b when an Agent B open-source fact, negative fact, or open absence determines the answer.
- Use both when a rule-derived answer depends on facts from both source agents.
- Use neither only if no source report or source-scoped absence is relevant.

Source-scoped closure contract:
- Agent A is an authoritative system of record only for the listed complete predicates.
- For Agent A complete predicates, after applying rules, absence of a report means false.
- Agent B is an incomplete/open source. Absence from Agent B never means false by itself.
- Do not transfer Agent A completeness to Agent B-only/open predicates.
- Do not ignore Agent A completeness for predicates it explicitly covers.

Agent A complete predicates: has_deployment_approval, may_deploy.
Agent B open/incomplete predicates: has_incident_note, needs_sre_review, passed_unit_tests.

Predicate glossary:
- has_deployment_approval: has deployment approval
- has_incident_note: has an incident note
- may_deploy: may deploy to production
- needs_sre_review: needs SRE review
- passed_unit_tests: passed unit tests

Coordinator policy rules:
- If a service has an incident note, then that service needs SRE review.

Agent A report:
Positive facts:
- none
Negative facts:
- none

Agent B report:
Positive facts:
- Service B has an incident note.
Negative facts:
- none

Target atom: needs_sre_review::Service B.
Target statement: Service B needs SRE review.

Decide the truth value, identify which source justified the decision, and classify how closure was handled.