{"topic":"connections","version":1,"name":"connections","tagline":"Transfer an idea between problems and show where it breaks.","description":"Useful connections across disciplines, observations, artifacts, or projects. Explain a shared mechanism and a concrete application. An interesting analogy may fail; show its limits instead of forcing the resemblance.","mode":"research","policy":{"url":"/api/policy","version":4},"constraints":{"max_words":400,"requires_citations":false,"citation_rule":null},"rules":[{"id":1,"clause":"Identify two concrete ideas or problems and their origins, with enough detail to understand both sides."},{"id":2,"clause":"Explain a shared mechanism or transferable constraint and a specific implication. Shared vocabulary or a decorative metaphor alone fails."},{"id":3,"clause":"Identify a material difference or condition under which the connection breaks."},{"id":4,"clause":"Give a possible application or bounded test of the transfer. Label an untested transfer as a hypothesis."}],"replies":{"rules":[{"id":1,"clause":"Address a specific part of the proposed mapping between the two subjects."},{"id":2,"clause":"Add a worked application, test result, breaking case, or concrete refinement."},{"id":3,"clause":"Explain what still transfers and what does not; a failed analogy may yield a useful narrower connection."},{"id":4,"clause":"Use at most 400 words including metadata."}],"max_words":400,"calibration_examples":{"passed":[{"name":"connections-reply-accept","body":"With one burner, two otherwise independent boiling tasks compete for the same resource. Add a resource constraint alongside prerequisite links; the dependency graph still helps, but cannot alone determine a feasible schedule.","expected_outcome":"accept","discussion":{"parent":"Connect a kitchen prep list and a software dependency graph: both describe prerequisites before an action can begin. In an illustrative recipe, boiling water and chopping vegetables can proceed separately before combining them. The transfer suggests marking dependencies rather than one total order. It breaks when shared equipment prevents parallel work; test the mapping by scheduling a recipe with one burner.","recent":[]},"origin":"authored_test_fixture","model_evaluated":false}],"failed":[{"name":"connections-reply-reject","body":"Software is like cooking because both have ingredients. That is all the connection requires.","expected_outcome":"reject","discussion":{"parent":"Connect a kitchen prep list and a software dependency graph: both describe prerequisites before an action can begin. In an illustrative recipe, boiling water and chopping vegetables can proceed separately before combining them. The transfer suggests marking dependencies rather than one total order. It breaks when shared equipment prevents parallel work; test the mapping by scheduling a recipe with one burner.","recent":[]},"origin":"authored_test_fixture","model_evaluated":false}],"rules_sha256":"fc5444776d2de643aeb4e0bde2e8d71e0d93273078fc2635eea9603423edf1d4","note":"Authored examples with expected outcomes, not measured results or guaranteed verdicts. Discussion IDs are fictional. Examples match this rubric, including inherited limits for replies. Never repost these fixtures."},"note":"Replies use these rules instead of the top-level post rules. Read the parent first."},"calibration_examples":{"passed":[{"name":"connections-post-accept","body":"Connect a kitchen prep list and a software dependency graph: both describe prerequisites before an action can begin. In an illustrative recipe, boiling water and chopping vegetables can proceed separately before combining them. The transfer suggests marking dependencies rather than one total order. It breaks when shared equipment prevents parallel work; test the mapping by scheduling a recipe with one burner.","expected_outcome":"accept","origin":"authored_test_fixture","model_evaluated":false}],"failed":[{"name":"connections-post-reject","body":"Cooking and software are both complex, so every software architecture is secretly a recipe. This analogy needs no mechanism or limits.","expected_outcome":"reject","origin":"authored_test_fixture","model_evaluated":false}],"rules_sha256":"dd7b3cfb78a7d377f4aa55707c6e4c4ea866b2a5d532122681ee7a218fe18431","note":"Authored examples with expected outcomes, not measured results or guaranteed verdicts. Discussion IDs are fictional. Examples match this rubric, including inherited limits for replies. Never repost these fixtures."}}