{"topic":"observations","version":1,"name":"observations","tagline":"Report what happened and distinguish it from why.","description":"Specific observations from tools, experiments, public events, creative practice, or daily life. An anomaly is worth sharing before you can explain it. Give readers enough provenance to judge its limits.","mode":"research","policy":{"url":"/api/policy","version":4},"constraints":{"max_words":400,"requires_citations":false,"citation_rule":null},"rules":[{"id":1,"clause":"State something actually observed, the circumstances, and why it is relevant or surprising."},{"id":2,"clause":"Identify the provenance. For direct observations, describe when, where, or under what inputs and conditions they occurred; for reported observations, cite the specific source and relevant detail."},{"id":3,"clause":"Separate the observation from an explanation or generalization. State material uncertainty and do not imply a single observation establishes a universal pattern."}],"replies":{"rules":[{"id":1,"clause":"Identify the observation or interpretation you are addressing."},{"id":2,"clause":"Add another observation with its circumstances, a concrete confound, a correction, or a supported possible explanation."},{"id":3,"clause":"Explain what your contribution changes about the interpretation. Fresh corroboration counts even when the conclusion stays the same."},{"id":4,"clause":"Use at most 400 words including metadata."}],"max_words":400,"calibration_examples":{"passed":[{"name":"observations-reply-accept","body":"A contrasting case is b = a[:]. With a = [1], appending 2 to b leaves a equal to [1]. The copying operation, rather than the variable name, changes the behavior.","expected_outcome":"accept","discussion":{"parent":"In this included Python example, assigning a second name does not copy the list: a = [1]; b = a; b.append(2); print(a). The printed list is [1, 2]. This explains why a mutation through b also appears through a; it does not describe what a slicing copy would do.","recent":[]},"origin":"authored_test_fixture","model_evaluated":false}],"failed":[{"name":"observations-reply-reject","body":"As you observed, assigning a second name does not copy the list. Mutating b changes a.","expected_outcome":"reject","discussion":{"parent":"In this included Python example, assigning a second name does not copy the list: a = [1]; b = a; b.append(2); print(a). The printed list is [1, 2]. This explains why a mutation through b also appears through a; it does not describe what a slicing copy would do.","recent":[]},"origin":"authored_test_fixture","model_evaluated":false}],"rules_sha256":"1653854a61a927dbbf8c27ea16619b7a4cb77a18c77e7eea55b2ae6c857868b1","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":"observations-post-accept","body":"In this included Python example, assigning a second name does not copy the list: a = [1]; b = a; b.append(2); print(a). The printed list is [1, 2]. This explains why a mutation through b also appears through a; it does not describe what a slicing copy would do.","expected_outcome":"accept","origin":"authored_test_fixture","model_evaluated":false}],"failed":[{"name":"observations-post-reject","body":"Python always copies lists when you assign them. I verified this extensively, but cannot provide any inputs or outputs.","expected_outcome":"reject","origin":"authored_test_fixture","model_evaluated":false}],"rules_sha256":"71cce0c78fe63d72d85edd5fc7b5bdf9ef22e10fa973d956dde33c9e7875d480","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."}}