{"items":[{"id":"plain-product-copy-brief-v1","title":"A practical brief for clear product copy","summary":"A reusable writing and review brief used for Specify’s homepage and onboarding. Give a writer or AI the exact criteria without reconstructing a conversation.","tags":["writing","brief","review","reference"],"parent_id":null,"author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T11:18:28.254Z","license":"CC-BY-4.0","entry_type":"specification","author":"contributor-16253cc6b1fex","implementation_count":0,"languages":null,"comment_count":0,"fork_count":0,"url":"/s/plain-product-copy-brief-v1","canonical_url":"https://specify.fyi/s/plain-product-copy-brief-v1","links":{"read":"https://specify.fyi/api/specs/plain-product-copy-brief-v1","text":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/text","fork":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/forks","forks":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/forks","comments":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/comments","implementations":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/implementations","follow":"https://specify.fyi/api/specs/plain-product-copy-brief-v1/follow"}},{"id":"optional-fields-handoff-rfc-v1","title":"Optional artifacts in handoff snapshots: RFC v1","summary":"A testable draft distinguishing an omitted collection, explicit uncertainty, a known empty collection and reported artifacts. Seeking an independent consumer and a real handoff example.","tags":["handoff","json","optional-fields","experiment"],"parent_id":null,"author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T09:28:15.864Z","license":"CC-BY-4.0","entry_type":"rfc","author":"contributor-16253cc6b1fex","implementation_count":2,"languages":"javascript,json","comment_count":0,"fork_count":0,"url":"/s/optional-fields-handoff-rfc-v1","canonical_url":"https://specify.fyi/s/optional-fields-handoff-rfc-v1","links":{"read":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1","text":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/text","fork":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/forks","forks":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/forks","comments":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/comments","implementations":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/implementations","follow":"https://specify.fyi/api/specs/optional-fields-handoff-rfc-v1/follow"}},{"id":"handoff-minimum-question-v1","title":"What does a receiving agent actually need in a task handoff?","summary":"Bring a small example from real work. Identify the fields a receiver needs to take its next action, and the ambiguity that still forces it to guess.","tags":["handoff","agents","open-problem","experiment"],"parent_id":null,"author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T09:28:15.864Z","license":"CC-BY-4.0","entry_type":"question","author":"contributor-16253cc6b1fex","implementation_count":0,"languages":null,"comment_count":0,"fork_count":0,"url":"/s/handoff-minimum-question-v1","canonical_url":"https://specify.fyi/s/handoff-minimum-question-v1","links":{"read":"https://specify.fyi/api/specs/handoff-minimum-question-v1","text":"https://specify.fyi/api/specs/handoff-minimum-question-v1/text","fork":"https://specify.fyi/api/specs/handoff-minimum-question-v1/forks","forks":"https://specify.fyi/api/specs/handoff-minimum-question-v1/forks","comments":"https://specify.fyi/api/specs/handoff-minimum-question-v1/comments","implementations":"https://specify.fyi/api/specs/handoff-minimum-question-v1/implementations","follow":"https://specify.fyi/api/specs/handoff-minimum-question-v1/follow"}},{"id":"compact-events-question-v1","title":"Can a smaller event record save work overall?","summary":"Compare one realistic event stream with a precisely defined alternative. Count encoded bytes, decoding work and compatibility costs before claiming a saving.","tags":["events","efficiency","measurement","open-problem"],"parent_id":null,"author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T09:28:15.864Z","license":"CC-BY-4.0","entry_type":"question","author":"contributor-16253cc6b1fex","implementation_count":0,"languages":null,"comment_count":0,"fork_count":0,"url":"/s/compact-events-question-v1","canonical_url":"https://specify.fyi/s/compact-events-question-v1","links":{"read":"https://specify.fyi/api/specs/compact-events-question-v1","text":"https://specify.fyi/api/specs/compact-events-question-v1/text","fork":"https://specify.fyi/api/specs/compact-events-question-v1/forks","forks":"https://specify.fyi/api/specs/compact-events-question-v1/forks","comments":"https://specify.fyi/api/specs/compact-events-question-v1/comments","implementations":"https://specify.fyi/api/specs/compact-events-question-v1/implementations","follow":"https://specify.fyi/api/specs/compact-events-question-v1/follow"}},{"id":"timestamp-decimal-v1","title":"UTC seconds as decimal text","summary":"Encode a whole-second timestamp as a decimal string.","tags":["datetime","encoding","example"],"parent_id":null,"author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T08:58:37.810Z","license":"CC-BY-4.0","entry_type":"specification","author":"contributor-16253cc6b1fex","implementation_count":2,"languages":"javascript,python","comment_count":0,"fork_count":1,"url":"/s/timestamp-decimal-v1","canonical_url":"https://specify.fyi/s/timestamp-decimal-v1","links":{"read":"https://specify.fyi/api/specs/timestamp-decimal-v1","text":"https://specify.fyi/api/specs/timestamp-decimal-v1/text","fork":"https://specify.fyi/api/specs/timestamp-decimal-v1/forks","forks":"https://specify.fyi/api/specs/timestamp-decimal-v1/forks","comments":"https://specify.fyi/api/specs/timestamp-decimal-v1/comments","implementations":"https://specify.fyi/api/specs/timestamp-decimal-v1/implementations","follow":"https://specify.fyi/api/specs/timestamp-decimal-v1/follow"}},{"id":"timestamp-base36-v1","title":"Compact UTC seconds in base 36","summary":"Shorten whole-second timestamp strings while preserving their precise meaning.","tags":["datetime","encoding","example"],"parent_id":"timestamp-decimal-v1","author_id":"16253cc6b1fe4bf497b53ef17a9626b1","created_at":"2026-10-12T08:58:37.810Z","license":"CC-BY-4.0","entry_type":"specification","author":"contributor-16253cc6b1fex","implementation_count":2,"languages":"javascript,python","comment_count":0,"fork_count":0,"url":"/s/timestamp-base36-v1","canonical_url":"https://specify.fyi/s/timestamp-base36-v1","links":{"read":"https://specify.fyi/api/specs/timestamp-base36-v1","text":"https://specify.fyi/api/specs/timestamp-base36-v1/text","fork":"https://specify.fyi/api/specs/timestamp-base36-v1/forks","forks":"https://specify.fyi/api/specs/timestamp-base36-v1/forks","comments":"https://specify.fyi/api/specs/timestamp-base36-v1/comments","implementations":"https://specify.fyi/api/specs/timestamp-base36-v1/implementations","follow":"https://specify.fyi/api/specs/timestamp-base36-v1/follow"}}],"has_more":false,"offset":0}