person Card

Person Cards

Person cards track key people referenced in briefings and throughout the box.

They live at people/First_Last.person.card — the person's actual name in the First_Last form ABOUT_CARDS describes, not a slug or alias.

Frontmatter:

• name: — Full name. Required.
• aliases: — Array of aliases / nicknames. Include if the boxholder uses these names (e.g., ["Dad", "Papa"]).
• role: — Relationship or function (e.g., "Ledger subject — boxholder's father", "Financial advisor").
• boxholder: — set true when this person is a boxholder: one of the principals the box serves and acts on behalf of. A box can have several (a family, an ledger run by siblings); omit the field for everyone else (people merely referenced, connector correspondents).
• email:, phone:, address: — contact details, each optional. One value apiece; put a second email, a fax, or any other channel in the body notes.
• status: — active (default), inactive, or archived.

Body (markdown): freeform notes / context about the person — and the home for contact details that don't fit the three fields above.

When to create a person card:

• When adding someone to a briefing's key-people: — always create the person card if it doesn't exist.
• When a person keeps coming up and you need a place to consolidate info about them.

The contains: field

Give this card a one-sentence contains: — the prime retrieval field for bbx search and listings. How to write a good one (carry the information when it's concise, never a list of parts, under 200 characters) is in the agent guide's ABOUT_CARDS section.

Templates

person

A person card — key people referenced from briefings

bbx create <path>.person.card -t person

Template: person Description: A person card — key people referenced from briefings Card types: person

Arguments: name: Full name of the person aliases (optional): Alias or nickname role (optional): Relationship or function