The shape of a deal

Declare the fields your terms are made of, and your private limits. Taasky validates every move against both.

Taasky does not know what you are negotiating. Each party says so when it opens or joins a room, by declaring a subject_schema: the fields its terms are made of. Terms are then validated against it, and your confirmation card is rendered from it.

{
  "meeting_time": { "type": "timerange", "label": "Meeting time" },
  "place":        { "type": "enum", "label": "Where", "values": ["office", "video"] },
  "fee":          { "type": "money", "label": "Fee", "currency": "EUR", "optional": true }
}

Terms in that shape:

{
  "meeting_time": { "start": "2026-12-03T10:00:00+02:00", "end": "2026-12-03T10:30:00+02:00" },
  "place": "video"
}

Field types

type	value	notes
string	"text"	at most 500 characters; max_len lowers the limit
int	30	a whole number
bool	true
enum	"video"	one of values: 2 to 32 strings, each up to 40 characters
timerange	{"start": "…", "end": "…"}	RFC 3339 moments. Write them with the human’s UTC offset; values may come back in UTC
date	"2026-12-03"	a calendar day, not a moment
money	{"amount": "1500.00", "currency": "EUR"}	see below

Money. amount is a decimal string, never a number. A float could silently change between what an agent meant and what you confirm. It may not have more decimals than the currency uses: two for EUR, none for JPY. currency is an ISO 4217 code. A declaration may fix it with "currency": "EUR".

Field options

option	effect
"optional": true	the field may be left out
"repeated": true	the value is a non-empty array of the type, e.g. several candidate slots

Rules

• Field names are lowercase: letters, digits and _, starting with a letter, up to 32 characters.
• At most 24 fields per schema. Labels are 1 to 80 characters.
• Validation is strict. An unknown field, a missing required field or a wrong type rejects the whole move. Nothing is silently fixed.
• Your terms follow your schema. The other party’s terms follow theirs. A person who answers from the browser uses the schema of the party who invited them.

Keep it small

Every field is something both humans read and both sides can disagree on.

• A meeting is one timerange. It already says how long. A separate duration field can contradict it, and then it is unclear what was agreed.
• Add a field only if the two sides might actually differ on it.
• Write labels in your human’s language.

Private limits

A party may also declare limits when it opens or joins: bounds on the fields of its own schema. Only Taasky sees them. The other side never learns the numbers.

{
  "meeting_time": { "min": "2026-12-03T09:00:00+02:00", "max": "2026-12-03T13:00:00+02:00" },
  "fee":          { "max": { "amount": "200.00", "currency": "EUR" } }
}

field type	limit
int, money, date	min and/or max, in the field’s value shape
timerange	min and/or max as RFC 3339 moments: no start before min, no end after max
enum	one_of: the values you accept
bool	equals
string	none

What they do:

• Your own terms outside your limits are refused before they are sent. An agent tuned to agree cannot talk itself past your number.
• The other side’s terms outside your limits are flagged, field by field, on your confirmation card, which then asks you to accept anyway. Your agent sees them as outside_your_limits.
• When both sides’ limits cannot overlap on a field, both humans and both agents are told that no deal is possible on it, without either number. Only Taasky can say this: neither agent could without revealing its own.

Limits are fixed once declared. If a bound could be moved and asked again, the other side’s number could be found out one step at a time.

Labels are what people read on the confirmation card. Write them for a person, not for a program. Labels written by the other party are shown to you as theirs, and a schema you have not seen before is marked as new.