--- title: "For an assistant — assignary" description: "An assistant reads your weekend and suggests a crew, on a credential you hand it and can take back. You still send the offers, and you still pay the crew." canonical: "https://assignary.com/assistant" --- for an assistant # Hand it a credential, not your sign-in. An assistant can read your weekend and suggest a crew: who is free, who is cleared, how far they would drive, what it pays. It runs on a credential you hand it, and you can take that back whenever you like. You still send the offers. You still pay the crew. can look - The Saturday Every game and panel on your books. Who is playing, where, when it starts, how many seats it needs, and what each seat pays. - Coverage What is still open, and who has already said yes. Which seats have an offer sitting out, and which are waiting on you. The same slate you are looking at, not a copy of it. - The roster Who works what, and what they are cleared for. Their sports, how far they will travel, and their clearances with the dates on them. That is how it can tell you why Nina is out of the 9 o’clock and who can take it instead. - A proposed crew A suggestion. Nothing has been sent. Who fits each open seat, why the rest are out, and the drive it would be for them. Sending the offer is still yours. after the weekend ## A chapter has to answer for it Who said yes is half of it. The rest is what you can show afterwards: the person in that seat was cleared for it, and the game got worked. - Clearances Cleared means they hold what the seat asks for, on the day it happens. Your chapter lists what each sport needs, by name — a referee badge, a judging certification — and a seat needs every name on its list, not one of them. Somebody holds it when the name matches, it has not been revoked, and it has not run out as of the moment the game starts rather than as of today: a badge lapsing next week still works tomorrow’s match and not next month’s panel. It is checked three times over — when an assigner offers the seat, when assignary asks the next person, and again at accept, because an offer can sit unanswered while a badge runs out. A refusal is never blocked; only taking the seat is. Recording one and verifying it are different acts: recording is who typed in what somebody said, verifying is a named person who says they went and checked. assignary never contacts the issuing body, so what the record shows is who vouched for it and when. - Outcomes Worked, no-show, or excused — marked against the seat. An assigner marks it, not the official: somebody saying they worked their own seat is a different product with a different trust story. Only a seat that was accepted can carry one, and once every accepted seat on an event has an answer the event closes itself — an open seat does not hold it back, because a game short a judge still happened. It changes what you owe: a weekend settlement pays worked seats, and a no-show or an excused seat is refused by name. - The trail Every move on a seat leaves a row saying who made it. Offered, accepted, declined, lapsed, escalated, withdrawn, marked, disputed — each one writes a row naming the chapter, the seat or position it happened to, and who did it. Where assignary moved a seat on its own, with nobody present, it signs as itself rather than borrowing somebody’s name, and files the move against the seat rather than against an id it does not have. A credential acting for somebody is recorded as a different fact from that person acting. Three of the moves are written with their row or not at all — a yes, an outcome, and a game called off — so a seat somebody took is a seat with a line about it. It is read one event at a time, beside the event somebody is already looking at, and it is an assigner’s to read: a trail naming every member and what each of them did is not a colleague’s business. - A disagreement The official can say the record is wrong, and the money waits. The outcome is an assigner’s to write, so this is the whole of what the official can say back: their own words on their own seat, and only on a seat something has been recorded about — there is nothing to disagree with until there is an answer to disagree with. Raising one stops the money. The weekend settlement leaves that seat out, and settling that one seat on its own is refused with a sentence rather than quietly doing nothing, because paying over a disagreement nobody has read decides it in the direction of whoever wrote the record. Two ways out and both are the assigner’s: change the outcome, which answers the disagreement in the same write, or read it and leave the record as it stands. Nothing expires it, because a timer would settle it in the same direction the missing check did. What the official wrote is the assigner’s to read and not the rest of the crew’s. - A receipt An official can take their own record with them. It is a signed document about one person in one chapter, drawn by that person: offers, accepts, how quickly they answer, whether the work happened, and the clearances they hold that have not been withdrawn. Every number is counted from stored columns rather than typed by anyone, and no pay figure travels in it at all. It is a signed JSON web signature — Ed25519, the format their tools already read — so checking it takes no code written for us. Whoever they hand it to checks it against the public keys published at the deployment’s own address, and needs nothing else from us — there is no verification endpoint to call, deliberately, because a reader who has to ask the issuer whether the issuer is telling the truth has gained nothing. If a deployment holds no signing key it refuses to draw one; it never issues an unsigned document, which would carry no more weight than a screenshot. - A standing check One clearance, asked about later, by somebody with an account. A signed receipt cannot know a clearance was pulled the week after it was drawn, so each one in it carries a one-off reference nobody can guess, which can be asked about. The answer is one of four words — valid, expired, revoked, unknown — with the time it was asked, and nothing else: no name, no chapter, no official, no history. Unknown and revoked are kept apart, because telling somebody a credential was withdrawn when it never existed is its own kind of lie. Two honest limits: the caller needs an assignary account, so this is not open to any passer-by; and valid means recorded, unexpired and not withdrawn — never that anyone confirmed it with the body that issued it. can answer - Take or refuse a seat An offer that was sent to them, answered either way. It answers as the person whose credential it is — their offers, nobody else’s. A yes re-checks their clearances against the day the game starts, because one can lapse while an offer sits unanswered. Saying no is always open to them: a seat held by somebody who cannot work it and cannot say so is worse than the lapse. - Say when they are free And when they are not. Hours, not answers. It changes who can be offered a seat, never who is — you still send every offer. Saying yes in advance is a separate thing, and the official sets it themselves: a matching offer is theirs the moment you send it, rather than after it has sat out its clock. Only for the person whose credential it is. yours to hand over - Offer a seat Who gets asked stays yours to decide. A credential can be given this, and only by somebody who holds it themselves — it is never wider than the person who issued it, and it narrows the moment their own role does. When a seat goes unanswered, assignary offers the next person itself, which is a rule you set rather than a credential acting for you. - Withdraw an offer Pulling a seat back once it is out. Every move on a seat is written down with the name of whoever made it, and a credential acting for you is recorded as itself — the trail names the key, not just your account. That is what makes handing this over something you can audit rather than something you have to trust. - Record who worked Worked, no-show, or excused. The outcome is what your chapter answers with afterwards. A credential can write it, and the official it is about can dispute what was written — which is the check that matters more than who typed it. - Pay anyone Money out, in every direction. Settling a seat is the one path that moves money, and it needs the owner’s own scope. Nothing mints a credential for a caller that asks for one: a person issues it, to something specific, and takes it back — and revoking it stops the next request rather than waiting for an expiry. Those stay yours to hand over. Nothing takes them without you. There is no way for something to ask us for access to your chapter. You issue the credential, scoped to what you choose, and you take it back — which stops the next request it makes, not the one after its expiry. how it gets in ## A credential you issue You pick what it can do, for one chapter, until a date you set. If something helps you assign — an assistant you already talk to — you hand it a credential rather than your sign-in. It is not a copy of your account: one chapter, the jobs you picked, and a date it stops on. - Only what you picked The jobs you picked, and nothing beside them. It is worked out again every time it asks assignary for anything: what your own role allows, narrowed to the jobs you picked, narrowed to the one chapter you issued it for. It can never do more than you can — and never more than the smallest of the three. - It narrows when you do Turn your own role down and it turns down with you. Nothing is fixed at the moment you issue it. Lower your own role and every credential you issued is narrower on its next request. Leave the chapter, or be taken off it, and they stop working altogether. It borrows your authority rather than keeping a copy of it. - One chapter The one you issued it for, and no other. The chapter on the credential is checked against the chapter being asked about, every time. Without that, one issued for the soccer club would reach the cheer circuit as well — and plenty of assigners work two. - It cannot widen itself It passes on less than it holds, or nothing. A credential allowed to issue another passes on only what it already holds, and the chain can only run so far. Without that limit it runs forever, and nobody reads to the end of a chain. - Your account stays yours Signing up, signing in, closing an account. A credential is turned away from anything about who you are — signing up, putting your details right, closing the account. It carries your authority for the work. The work is not your account. - Revoked means now The next request, not the next expiry. Every request looks the credential up rather than taking it at face value, so taking it back stops it on the next one. Only a fingerprint is kept, and the credential itself is shown once, when you issue it — a stored copy would be a drawer holding everybody’s keys. Take it back and the very next request is turned down. You do not wait for it to expire. [Start a crew](https://app.assignary.com/sign-up?for=crew) [How it works](https://assignary.com/how) [What is stored](https://assignary.com/privacy)