MyJackfruit

Help
Browse topics · Starting

Starting

← Starting

How do I write a Constraint in my plan?

Short answer

Press Main menu, choose Plan, press + New, choose a constraint, search and select the person, type a tag (its short name), press Create.

Before you start

You need to be signed in to GilbApp on a computer, with a vault you can write to, such as your own vault. You also need the name of the person who requires the constraint. The pictures show a made-up person on a test site; your screen shows your own name and address.

Words used here (8)
short name
A short name is the one word you give one AI on one computer, such as gilb-example; it keeps that AI's key and tools apart.
GilbApp
GilbApp is the app, opened in a web browser at https://gilb.com/app, where you open, fill and share your vaults.
Kai-Zen
Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
record
A record is one piece of data with its own address, such as a person, a place, a thing or a note.
virtual folder
A virtual folder is a view that groups records and files without moving them; each may sit in several folders.
field
A field is one named fact on a record, such as its title or a due date; its name comes from GilbVeda.
assumption
An assumption is a choice Kai-Zen made for you, or a fact your plan counts on, written down so you can check or change it.
Part of System
Part of System is the line on a Solution's card that names the one system the Solution belongs to, such as an app.
Steps
  1. Press Main menu at the top left and choose Plan.

    Press Main menu, next to your profile picture at the top left, and under YOUR SECTIONS choose Plan. The button shows the name of the section you are in, such as Vaults.

    GilbApp with the "GO TO" panel open, and "Plan" under "YOUR SECTIONS" outlined in orange.
    GilbApp with the "GO TO" panel open, and "Plan" under "YOUR SECTIONS" outlined in orange.
    Show as text

    In the GO TO panel that opens from "Main menu" at the top left, look under YOUR SECTIONS on the left. The outlined row is "Plan", with the line "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." Press it to open the Plan screen.

    More about this

    A panel headed GO TO opens; Plan reads Your Kai-Zen plan: Functions, Values, Development Resources and Solutions. You can also press the Plan button on the card of a vault (the place where a person or a group keeps their records) in Vaults. The Plan screen lists your plan records and has the views Grid, Graph, Both and Card.

  2. Press + New.

    Press + New at the top right of the Plan screen. With no record selected, the type dialog opens at once.

    The "Plan" screen with the list of plan records and no record selected, with the "+ New" button at the top right outlined in orange.
    The "Plan" screen with the list of plan records and no record selected, with the "+ New" button at the top right outlined in orange.
    Show as text

    Look at the top right of the Plan screen, just left of the Details pane. The outlined button is "+ New". Press it; with no record selected a dialog headed "New function" opens with its "TYPE" list.

    More about this

    If a record is selected, New first offers five choices: Create a record and link it to the selected record, Link the selected record to a record that already exists, Create a record on its own, Create a virtual folder and Upload a file. Choose Create a record on its own. A new constraint needs nothing else; the others make a record joined to the selected one, link two records that already exist, make a virtual folder or upload a file. In Plan, the GO TO panel also has New plan record, which does the same.

  3. Under TYPE, choose Function Constraint or Solution Constraint.

    In the list under TYPE, choose Function Constraint for something the system must do, or Solution Constraint for a way it must be done. A constraint is something that must be done because a named person requires it.

    The new-record dialog headed "New function" with the list under "TYPE", with the "Function Constraint" option outlined in orange.
    The new-record dialog headed "New function" with the list under "TYPE", with the "Function Constraint" option outlined in orange.
    Show as text

    In the dialog headed "New function", look at the list under "TYPE". The outlined row is "Function Constraint", just under "Function". Click it, or "Solution Constraint" further down for a Solution Constraint.

    More about this

    The dialog opens headed New function; after you choose a constraint it is headed New function constraint or New solution constraint. Choose the type first: a type that is not a constraint clears a person you picked in step 4. The chosen type then shows under TYPE with a DEFINITION read from GilbVeda, the shared list of terms; it can be long, and you need not read it. × beside the type brings the list back. A search box above the TYPE list narrows it as you type, and Close at the top of the dialog closes it like Cancel; you need neither. ↗ at the end of a row shows what GilbVeda says about that type; you do not need it. Cancel closes the dialog without making anything. Where it shows Back instead, Back returns you to the five choices.

  4. Under AUTHORITY, search and select the person who requires it.

    Under AUTHORITY, type in the box that shows Search people and select the person who requires the constraint. An Authority is that named person.

    The dialog headed "New function constraint" with the avoid line and the "AUTHORITY required" block above "TAG", with the "Search people" box outlined in orange.
    The dialog headed "New function constraint" with the avoid line and the "AUTHORITY required" block above "TAG", with the "Search people" box outlined in orange.
    Show as text

    The dialog is now headed "New function constraint". Under the definition and the line "Avoid constraints where you can…", the block "AUTHORITY required" holds the outlined box "Search people". Type part of the person's name and select them. "Create" stays grey until you do.

    More about this

    The label reads AUTHORITY required, and the dialog adds "Avoid constraints where you can: each one locks out options. Record one only when a named person requires it." Create stays greyed until you choose a person; hover on it to see A constraint's Authority is the named person who requires it. Only people are listed, from your vaults, up to eight at a time; Type to search all says there are more. A button starting with Remove takes the chosen person back. If none matches, the list says No person record matches. Press + New stakeholder to add the person: a dialog for a new person opens, and when you create them they are chosen here.

  5. Type a tag in TAG and press Create.

    Type a tag in TAG, check CREATE IN, and press Create. A tag is the short name of a plan record: an area, a dot and a keyword, such as Members.KeepPrivate.

    The dialog with the person chosen, a tag typed under "TAG" and the vault under "CREATE IN", with the "Create" button outlined in orange.
    The dialog with the person chosen, a tag typed under "TAG" and the vault under "CREATE IN", with the "Create" button outlined in orange.
    Show as text

    The person's name now shows under "AUTHORITY required" with a "Remove" link, and "TAG" holds your tag. At the bottom right, the outlined button "Create" is active. Press it.

    More about this

    With the tag empty the screen says Give it a Tag first: a Plan card is named by its Tag. Under CREATE IN, choose the vault where it will live; vaults you can only read say read only, you cannot create there. If the tag is already used in that vault, the screen says is already used in this vault. Pick another. If the vault is not the one you are viewing, the dialog stays open and says the record was made there, not in the vault you are viewing. It is not drawn here., with an Open it button. If it says The constraint was made, but its Authority was not linked: add it on the card., close the dialog and add the person on the card. Leave More function constraint details (for a Solution Constraint, More solution constraint details) closed: the card's own Description is written in parts (step 7).

  6. If it is a Function Constraint, under Level, choose Product.

    If you made a Function Constraint, open the list next to Level on the line under the card's header and choose Product. A level says which part of the plan the constraint belongs to.

    The new constraint's card in edit mode, with the "Level" list on the line under the card's header outlined in orange.
    The new constraint's card in edit mode, with the "Level" list on the line under the card's header outlined in orange.
    Show as text

    On the new constraint's card, the line under "FUNCTION CONSTRAINT" reads "Type: Function / Function Constraint · Level: · Version:". The outlined "Level" list is empty. Open it and choose "Product". The person shows under "Authority" with "required".

    More about this

    After Create, the new constraint opens in edit mode: Done is at the top right of the card and the card says Editing. Changes save as you leave a field. There is no Save button. If you come back later, click the constraint in the list and press Edit. The method puts a Function Constraint at Product. A Solution Constraint shows Solution until you choose another level; leave it. The list holds Business, Stakeholder, Product and Solution by default, and + Add level… for one of your own. The same line shows Type (two radio buttons, with your choice from step 3 marked) and Version (a date); you need neither. The level is not needed to save.

  7. Under Description, press + Part, type a Keyword and Text, and press Add.

    Under Description, press + Part, type a Keyword and the Text, and press Add. A Description says what the constraint requires, one short part at a time.

    The constraint's card with the level "Product" chosen and an empty "Description", with the "+ Part" button outlined in orange.
    The constraint's card with the level "Product" chosen and an empty "Description", with the "+ Part" button outlined in orange.
    Show as text

    With "Product" chosen, look at "Description", which reads "No description yet". The outlined button is "+ Part". Press it, type a "Keyword" and "Text", and press "Add".

    More about this

    Say what must be done, or how, as a plain statement; the person who requires it is already in Authority. The Keyword is one word: letters only, starting with a capital, such as Private; otherwise the screen says Keyword: letters only, starting with a capital, e.g. Sync. If you type the Text first, the box suggests its first word as the Keyword. Each part gets its own tag: the constraint's tag, a dot, the Keyword. With nothing yet, the line reads No description yet. Discard throws away the part you typed (the screen then asks Discard what you typed? with Keep and Discard); you do not need it. It is not needed to save.

  8. If you need more, press + Assumption or Paste parts.

    If you need more, under Description, press + Assumption or Paste parts. + Assumption adds something the constraint counts on, and Paste parts adds many parts at once.

    The constraint's card with one part under "Description", with the "+ Assumption" button outlined in orange.
    The constraint's card with one part under "Description", with the "+ Assumption" button outlined in orange.
    Show as text

    The part shows under "Description". Below it, the outlined button is "+ Assumption", between "+ Part" and "Paste parts". Press it, or "Paste parts", only if you need more.

    More about this

    An assumption is a plain claim a test can prove wrong: no may, might, could or expected to. In the Paste parts box, write one part per line as Keyword: text, then press the button that starts with Create. A ? button next to + Part, + Assumption and Paste parts opens help about the Description; you do not need it. Once a part is added, its row has ↑ and ↓ to move it up or down, → and ← to move it under the part above (a sub-part) or out one level, × to remove it, and a grip to drag it; you need them only to rearrange. Under the Paste parts box, Discard throws away what you pasted; you do not need it. None is needed to save.

  9. Press Done when you have finished.

    Press Done at the top right of the card. What you typed is already saved.

    The constraint's card at the top, still in edit mode, with "Done" at the top right outlined in orange.
    The constraint's card at the top, still in edit mode, with "Done" at the top right outlined in orange.
    Show as text

    The card is scrolled to the top and is still in edit mode. At the top right, beside the box with the tag, the outlined word is "Done". Press it when you have finished; each field was saved when you left it.

    More about this

    The card also has optional lines: Stakeholder (who has a stake in it), Meter (how a person, an AI or a test checks it) and Status (press + New status). A Function Constraint also has Part of; a Solution Constraint also has Solution of Function, Part of System and Impacts. They work as on a Function or a Solution; the answers on writing a Function in your plan and on writing a Solution in your plan show them. Authority shows the person you chose and the word required; a person you add there gets an optional acts for line. Each of these lines has an optional Source box. Beside Done, a + does what + Add Information at the foot of the card does; you do not need it. It can bring back a second Type line: the kind of thing the constraint is about, from the types in GilbVeda.

Deeper

Also asked:

What is an Authority? The named person who has the power to decide, influence or enforce something in your plan. A constraint needs one, a person, not a role or a group; on a Function, a Solution or a Value the Authority line is optional.

A constraint needs only a tag and one person, its Authority. Every other line on the card is optional.

Avoid constraints where you can. Each one locks out other ways of doing the work, so write one only when a named person requires it.

The tag is the constraint's name. It cannot be left empty, and a tag already used in the same vault is refused.

The Authority must be a person, not a role or a group. The card keeps at least one: removing the last is refused with "A constraint needs the named person who requires it. Change the Type to Function instead, or add another Authority first."

To turn a Function or a Solution you already have into a constraint, open its card. Under Type, choose the radio button Function Constraint (on a Solution, Solution Constraint); if the card is not in edit mode, press the type word there first to show the two radio buttons. Search and select a person if the card has none, and press Change.

A Value's Tolerable limit (the worst number you can live with) and its Goal (the number you plan to reach) are constraints too. A Value is a perceived benefit, measured as a number. You write them as numbers in its Levels (the numbers on its Scale, the ruler the Value is measured on), not on a constraint card.

A deadline is a limit on time, and time is a Development Resource, something your plan spends, such as time or money: its Budget is the most time you plan to use, a limit the plan must keep. The answer on writing a Resource and setting the project's currency shows how.

A law or another rule your app must keep has no person of its own: as its Authority, name the person who requires that your app keeps it. See: Do I have to follow rules such as GDPR or app store rules from the start?

This answer is written for a computer screen.

Checked against GilbApp d529620.