Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,537Letters: 14Defects: 1,323counted 3 min ago
teppi

Server definition

Hash
sha256:9d87e376b1c5302c00a3f5d2141489cb75992bc77a1ba1b203bbacceceb58647
What it is
What a remote MCP server returned when asked what it offers: 6 tools

The blob, as servednamed by its sha256

{ "instructions": "What Matters is the user's personal list of action items.\n\nSECTIONS — every item lives in exactly one. action = the user owes the next\nmove. waiting = owed TO the user; someone else moves next. note = worth\nknowing, no action. If the ball is in someone else's court it is waiting.\n\nNo \"today\" section: anything due today or earlier surfaces at the top, so\nset \"due\" only for real deadlines. channel = where an item ORIGINATED\n(self/teams/email/meeting/other), not who typed it. priority defaults to\nmedium; \"high\" only when someone is blocked or a deadline is close — mark\neverything high and the signal dies. note = prose context; links = up to 3\n{label, url}, never raw URLs in the note. Never touch \"settings\".\n\nTWO WRITE PATHS. Scheduled or autonomous runs: get_document, then\nput_proposal — nothing lands until the user reviews it; set \"agent\" to your\nname (\"Claude\"), it headlines the review. Max 100 deltas; send the ones that matter. Live conversation, user\nasking directly: add_item / complete_item write straight through, with\ninitiated \"human\" (\"the user\" = whoever is talking to you, any account).\n\nTHE URGENT PUNCH-THROUGH: add_item with initiated \"auto\" AND priority \"high\"\npushes a notification to the user's phone — the ONE sanctioned bypass of\nreview. Only for someone-blocked-right-now; routine\nurgency kills the signal. Lower-priority auto adds land silently. ALWAYS\nstamp source_id on auto adds when a stable message or event id exists — the\ndedup key that stops the same thing being re-added under a reworded title.\n\nNever re-suggest anything deleted or in \"rejections\" — a dismissal is an\nanswer. Active rules are enforced server-side; put_proposal reports drops.\n\nFOCUS — \"focus\" is up to 10 short terms the user says matter most. Weigh\nthem in what you notice; it does NOT move an item's section or make it\nurgent. Set it only when the user asks, via manage_focus; never invent one.\n\nCondensed. Full guide — rules syntax, rejection→rule mining, fingerprints —\nis guide://what-matters; read it before any scheduled run.", "tools": [ { "description": "Add an item immediately, without review. Normally use this ONLY when the user has just asked for it in conversation — they are the human in the loop at that moment, so set initiated: \"human\". Anything found by scanning on a schedule belongs in put_proposal instead, with ONE exception: something genuinely urgent that cannot wait for review may be added with initiated: \"auto\" and priority: \"high\", which immediately notifies the user's phone. That interruption is the point — reserve it for things that truly cannot wait, because routine \"urgent\" adds teach the user to ignore the one signal that means look now.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "due": { "description": "YYYY-MM-DD.", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "type": "string" }, "flagged": { "description": "True marks the task as urgent — needing the user’s attention now. Set it only when the user asked for the flag, or something genuinely cannot wait; it changes no ordering and no due date.", "type": "boolean" }, "initiated": { "description": "Who set this add in motion. \"human\" = the user asked for it in this conversation — whoever is talking to you, not one specific person. \"auto\" = you are adding it on your own initiative with no direct instruction. Be truthful: \"auto\" combined with priority \"high\" interrupts the user's phone.", "enum": [ "human", "auto" ], "type": "string" }, "links": { "description": "Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note.", "items": { "properties": { "label": { "description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL.", "maxLength": 80, "minLength": 1, "type": "string" }, "url": { "description": "The full URL, http or https only. Up to 1000 characters.", "format": "uri", "maxLength": 1000, "type": "string" } }, "required": [ "label", "url" ], "type": "object" }, "maxItems": 3, "type": "array" }, "note": { "description": "Prose context, markdown. A URL belongs in `links`, not here.", "maxLength": 10000, "type": "string" }, "priority": { "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" }, "source": { "description": "Who it involves or where it came from — \"Dana\", \"Tuesday's standup\".", "maxLength": 200, "type": "string" }, "source_id": { "description": "The stable id of whatever this came from — a Teams message id, an Outlook internetMessageId, a calendar event id. Set it whenever you have one: it is how the app recognises the same thing again, across runs and after rewording.", "maxLength": 500, "type": "string" }, "title": { "description": "The thing to do.", "maxLength": 500, "minLength": 1, "type": "string" } }, "required": [ "title", "section", "initiated" ], "type": "object" }, "name": "add_item", "outputSchema": null }, { "description": "Mark an item done, or reopen it. Idempotent.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "done": { "description": "Default true.", "type": "boolean" }, "item_id": { "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" } }, "required": [ "item_id" ], "type": "object" }, "name": "complete_item", "outputSchema": null }, { "description": "Read everything: action items, the record of what has already been dismissed, and \"focus\" — the handful of terms the user says matter most. Always call this before proposing changes: it is the only way to know what was already deleted or rejected, and re-suggesting those is the main failure mode.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "include_dismissed": { "description": "Include deleted items and previously rejected suggestions. Default true, and you almost always want it: this is how you avoid proposing something again.", "type": "boolean" }, "include_rules": { "description": "Include the standing rules. Default true. Read them: the server drops any suggestion an active rule excludes, so proposing one is wasted effort.", "type": "boolean" } }, "type": "object" }, "name": "get_document", "outputSchema": null }, { "description": "Replace the list of things the user says matter most — people, projects, whatever they care about. Send the WHOLE list every time, including the terms you are keeping: this replaces, it does not append, so omitting one deletes it. Read the current list from get_document first. Up to 10 terms of 60 characters; longer lists and longer terms are trimmed rather than refused, and the stored result comes back so you can see what landed. ONLY call this when the user asks you directly, in conversation. A scheduled run must never touch it: focus is the user saying what they care about, so a term they did not choose is worse than no term at all. Never infer one from their list.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "terms": { "description": "The complete list, in the order the user wants to see it. An empty array clears it.", "items": { "type": "string" }, "type": "array" } }, "required": [ "terms" ], "type": "object" }, "name": "manage_focus", "outputSchema": null }, { "description": "Create, change, pause or delete a standing rule, taking effect IMMEDIATELY with no review. Use this only when the user asks you directly — \"stop suggesting PTO stuff\". A scheduled run must propose rules through put_proposal instead, exactly as it proposes items rather than calling add_item.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "operation": { "enum": [ "create", "update", "pause", "resume", "delete" ], "type": "string" }, "patch": { "description": "Fields to change, for update.", "properties": { "action": { "enum": [ "exclude", "recategorize", "always_keep", "boost" ], "type": "string" }, "match": { "properties": { "conditions": { "items": { "properties": { "field": { "enum": [ "section", "channel", "source", "title", "priority", "due_relative" ], "type": "string" }, "op": { "enum": [ "equals", "not_equals", "contains" ], "type": "string" }, "value": { "items": { "maxLength": 200, "type": "string" }, "maxItems": 20, "minItems": 1, "type": "array" } }, "required": [ "field", "op", "value" ], "type": "object" }, "maxItems": 10, "minItems": 1, "type": "array" }, "op": { "default": "all", "enum": [ "all", "any" ], "type": "string" } }, "required": [ "conditions" ], "type": "object" }, "params": { "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "priority": { "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" } }, "type": "object" }, "reason": { "description": "Why this rule exists, in the user's terms. Shown next to it on the rules page.", "maxLength": 300, "minLength": 1, "type": "string" }, "status": { "enum": [ "active", "paused" ], "type": "string" } }, "type": "object" }, "rule": { "description": "Required for create.", "properties": { "action": { "enum": [ "exclude", "recategorize", "always_keep", "boost" ], "type": "string" }, "match": { "properties": { "conditions": { "items": { "properties": { "field": { "enum": [ "section", "channel", "source", "title", "priority", "due_relative" ], "type": "string" }, "op": { "enum": [ "equals", "not_equals", "contains" ], "type": "string" }, "value": { "items": { "maxLength": 200, "type": "string" }, "maxItems": 20, "minItems": 1, "type": "array" } }, "required": [ "field", "op", "value" ], "type": "object" }, "maxItems": 10, "minItems": 1, "type": "array" }, "op": { "default": "all", "enum": [ "all", "any" ], "type": "string" } }, "required": [ "conditions" ], "type": "object" }, "origin": { "properties": { "count": { "default": 0, "maximum": 9007199254740991, "minimum": 0, "type": "integer" }, "from": { "enum": [ "rejections", "manual" ], "type": "string" }, "rejection_ids": { "default": [], "items": { "type": "string" }, "maxItems": 50, "type": "array" } }, "required": [ "from" ], "type": "object" }, "params": { "default": {}, "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "priority": { "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" } }, "type": "object" }, "reason": { "description": "Why this rule exists, in the user's terms. Shown next to it on the rules page.", "maxLength": 300, "minLength": 1, "type": "string" }, "status": { "enum": [ "active", "paused" ], "type": "string" } }, "required": [ "action", "match", "reason", "origin" ], "type": "object" }, "rule_id": { "description": "Required for update, pause, resume and delete.", "type": "string" } }, "required": [ "operation" ], "type": "object" }, "name": "manage_rule", "outputSchema": null }, { "description": "Replace the pending set of suggested changes. This is the ONLY write the scheduled run should make — nothing here reaches the list until the user reviews and accepts it. Replaces any previous proposal wholesale, so include everything still worth suggesting, up to 100 deltas.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "agent": { "description": "Your name as the user knows you — \"Claude\" — shown as the review headline (\"Claude suggests some changes\") and in the notification. Just the name: no model version, no \"AI\". Omit it and the screen says \"Your AI agent\".", "maxLength": 40, "minLength": 1, "type": "string" }, "deltas": { "description": "The proposed changes — add, complete, remove or update, plus the rule kinds. At most 100: send the ones that matter most and let the rest wait for the next run, because a review too long to finish gets dismissed whole. An empty array clears the proposal. Prefer complete over remove for anything that actually got done.", "items": { "oneOf": [ { "description": "Suggest a new item the user does not have yet.", "properties": { "item": { "properties": { "channel": { "default": "self", "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "due": { "description": "YYYY-MM-DD. Anything dated today or earlier surfaces in the Today section, so only set this when there is a real deadline — a speculative date drags it to the top.", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "type": "string" }, "flagged": { "description": "True marks this task as urgent — needing the user’s attention now. The user toggles it in the app, and the daily briefing offers it on critical findings. It changes no ordering and no due date: a flag is attention, not a deadline. Set it only when something genuinely cannot wait; flag everything and it means nothing. Absent means not flagged.", "type": "boolean" }, "initiated": { "description": "Only two values, and only for AI adds. \"human\" = the user asked for this item in conversation just now — any user, whoever is talking to the MCP server, not one specific person. \"auto\" = the AI added it on its own initiative, with no direct instruction. Absent on items the user typed into the app themselves.", "enum": [ "human", "auto" ], "type": "string" }, "links": { "default": [], "description": "Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note: they render as buttons rather than as a wall of text.", "items": { "properties": { "label": { "description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL.", "maxLength": 80, "minLength": 1, "type": "string" }, "url": { "description": "The full URL, http or https only. Up to 1000 characters.", "format": "uri", "maxLength": 1000, "type": "string" } }, "required": [ "label", "url" ], "type": "object" }, "maxItems": 3, "type": "array" }, "note": { "description": "Optional detail or context, markdown. Leave empty unless it genuinely adds something. Up to 2000 characters — a paragraph or two, not a transcript.", "maxLength": 2000, "type": "string" }, "priority": { "default": "medium", "description": "How much this matters: low, medium or high. Defaults to medium — most things are medium, so use high only when someone is blocked or a real deadline is close, and low for things that genuinely can wait. Marking everything high makes the list useless.", "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" }, "source": { "description": "Who it involves or where it came from — \"Dana\", \"You → Dana\", \"Tuesday's standup\". Free text: sometimes a person, sometimes an occasion.", "maxLength": 200, "type": "string" }, "source_id": { "description": "The stable id of whatever this came from — a Teams message id, an Outlook internetMessageId, a calendar event id. Set it whenever you have one. It is how the app recognises the same thing again after you have reworded the title, which you are otherwise told to do.", "maxLength": 500, "type": "string" }, "status": { "description": "open or done. Leave it out for anything the user still has to act on — which is almost always. Send \"done\" only when adding something that ALREADY happened and is worth keeping as a record.", "enum": [ "open", "done" ], "type": "string" }, "title": { "description": "The thing to do, phrased as an action the user can act on. Prefer \"Reply to Dana about the audit dates\" over \"Dana email\". Keep it to one line — 200 characters at most, and anything approaching that belongs in the note instead.", "maxLength": 200, "minLength": 1, "type": "string" } }, "required": [ "title", "section" ], "type": "object" }, "kind": { "const": "add", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" } }, "required": [ "kind", "item" ], "type": "object" }, { "description": "Suggest an item is already DONE — the meeting happened, the reply was sent. This is almost always what you want when something looks finished. It keeps the record that he completed it; use remove only when the item should never have been there.", "properties": { "item_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" }, "kind": { "const": "complete", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" } }, "required": [ "kind", "item_id" ], "type": "object" }, { "description": "Suggest an item should be cleared without being done — a duplicate, or something that stopped being relevant. If it was actually finished, use complete instead.", "properties": { "item_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" }, "kind": { "const": "remove", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" } }, "required": [ "kind", "item_id" ], "type": "object" }, { "description": "Suggest changing fields on an existing item — a slipped due date, a better title. Include only the fields that change; anything omitted is left alone.", "properties": { "item_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" }, "kind": { "const": "update", "type": "string" }, "patch": { "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "due": { "anyOf": [ { "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "type": "string" }, { "type": "null" } ], "description": "YYYY-MM-DD. Anything dated today or earlier surfaces at the top, so only set this when there is a real deadline — a speculative date drags it up. Omit to leave the due date alone; null clears it." }, "flagged": { "description": "True marks this task as urgent — needing the user’s attention now; false clears the flag. It changes no ordering and no due date: a flag is attention, not a deadline. Set true only when something genuinely cannot wait. Omit to leave the flag alone.", "type": "boolean" }, "links": { "description": "Up to 3 named links — the thread, the document, the ticket. PUT URLS HERE, never pasted into the note: they render as buttons rather than a wall of text. Replaces the whole list, so include any existing links you want to keep. Omit to leave them alone.", "items": { "properties": { "label": { "description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL.", "maxLength": 80, "minLength": 1, "type": "string" }, "url": { "description": "The full URL, http or https only. Up to 1000 characters.", "format": "uri", "maxLength": 1000, "type": "string" } }, "required": [ "label", "url" ], "type": "object" }, "maxItems": 3, "type": "array" }, "note": { "anyOf": [ { "maxLength": 2000, "type": "string" }, { "type": "null" } ], "description": "Optional detail or context, markdown. Prose only — a URL belongs in `links`, not here. Up to 2000 characters. Omit to leave the note alone; null clears it." }, "priority": { "description": "How much this matters: low, medium or high. Use high only when someone is blocked or a real deadline is close, and low for things that genuinely can wait. Marking everything high makes the list useless. Omit to leave the current priority alone.", "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" }, "source": { "anyOf": [ { "maxLength": 200, "type": "string" }, { "type": "null" } ], "description": "Who it involves or where it came from — \"Dana\", \"You → Dana\", \"Tuesday's standup\". Omit to leave it alone; null clears it." }, "title": { "description": "The thing to do, phrased as an action the user can act on. Prefer \"Reply to Dana about the audit dates\" over \"Dana email\". Keep it to one line — 200 characters at most, and anything approaching that belongs in the note instead.", "maxLength": 200, "minLength": 1, "type": "string" } }, "type": "object" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" } }, "required": [ "kind", "item_id", "patch" ], "type": "object" }, { "description": "Suggest a standing rule, mined from a pattern in the rejections list. Only when 3 or more rejections share a trait and no active rule already covers it — one rejection is never a pattern. Never auto-applied: it does nothing until the user accepts it.", "properties": { "kind": { "const": "add_rule", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" }, "rule": { "properties": { "action": { "enum": [ "exclude", "recategorize", "always_keep", "boost" ], "type": "string" }, "match": { "properties": { "conditions": { "items": { "properties": { "field": { "enum": [ "section", "channel", "source", "title", "priority", "due_relative" ], "type": "string" }, "op": { "enum": [ "equals", "not_equals", "contains" ], "type": "string" }, "value": { "items": { "maxLength": 200, "type": "string" }, "maxItems": 20, "minItems": 1, "type": "array" } }, "required": [ "field", "op", "value" ], "type": "object" }, "maxItems": 10, "minItems": 1, "type": "array" }, "op": { "default": "all", "enum": [ "all", "any" ], "type": "string" } }, "required": [ "conditions" ], "type": "object" }, "origin": { "properties": { "count": { "default": 0, "maximum": 9007199254740991, "minimum": 0, "type": "integer" }, "from": { "enum": [ "rejections", "manual" ], "type": "string" }, "rejection_ids": { "default": [], "items": { "type": "string" }, "maxItems": 50, "type": "array" } }, "required": [ "from" ], "type": "object" }, "params": { "default": {}, "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "priority": { "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" } }, "type": "object" }, "reason": { "description": "Why this rule exists, in the user's terms. Shown next to it on the rules page.", "maxLength": 300, "minLength": 1, "type": "string" }, "status": { "enum": [ "active", "paused" ], "type": "string" } }, "required": [ "action", "match", "reason", "origin" ], "type": "object" } }, "required": [ "kind", "rule" ], "type": "object" }, { "description": "Suggest changing an existing rule — usually to narrow one that is too broad.", "properties": { "kind": { "const": "update_rule", "type": "string" }, "patch": { "properties": { "action": { "enum": [ "exclude", "recategorize", "always_keep", "boost" ], "type": "string" }, "match": { "properties": { "conditions": { "items": { "properties": { "field": { "enum": [ "section", "channel", "source", "title", "priority", "due_relative" ], "type": "string" }, "op": { "enum": [ "equals", "not_equals", "contains" ], "type": "string" }, "value": { "items": { "maxLength": 200, "type": "string" }, "maxItems": 20, "minItems": 1, "type": "array" } }, "required": [ "field", "op", "value" ], "type": "object" }, "maxItems": 10, "minItems": 1, "type": "array" }, "op": { "default": "all", "enum": [ "all", "any" ], "type": "string" } }, "required": [ "conditions" ], "type": "object" }, "params": { "properties": { "channel": { "description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email.", "enum": [ "self", "teams", "email", "meeting", "other" ], "type": "string" }, "priority": { "enum": [ "low", "medium", "high" ], "type": "string" }, "section": { "description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists.", "enum": [ "action", "waiting", "note" ], "type": "string" } }, "type": "object" }, "reason": { "description": "Why this rule exists, in the user's terms. Shown next to it on the rules page.", "maxLength": 300, "minLength": 1, "type": "string" }, "status": { "enum": [ "active", "paused" ], "type": "string" } }, "type": "object" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" }, "rule_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" } }, "required": [ "kind", "rule_id", "patch" ], "type": "object" }, { "description": "Suggest deleting a rule outright.", "properties": { "kind": { "const": "remove_rule", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" }, "rule_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" } }, "required": [ "kind", "rule_id" ], "type": "object" }, { "description": "Suggest pausing a rule, leaving it in the list so it can be resumed.", "properties": { "kind": { "const": "pause_rule", "type": "string" }, "reason": { "description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\".", "maxLength": 500, "type": "string" }, "rule_id": { "description": "The \"id\" of an existing item, exactly as returned by get_document.", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", "type": "string" } }, "required": [ "kind", "rule_id" ], "type": "object" } ] }, "type": "array" }, "summary": { "description": "One line on what this pass looked at.", "maxLength": 1000, "type": "string" } }, "required": [ "deltas" ], "type": "object" }, "name": "put_proposal", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:9d87e376b1c5302c00a3f5d2141489cb75992bc77a1ba1b203bbacceceb58647 | sha256sum