# Example: Neighborhood Tool Library Service This example shows Domain Context Modeling used manually for a physical community service. No AI feature or AI-assisted workflow is required. ## Working Context A neighborhood association wants to create a shared tool library where members can borrow household, gardening, and repair tools. A facilitator uses the Core Brief in a workshop with volunteers, prospective members, and the association treasurer before choosing software or buying inventory. The working group completes the brief on a shared document and a wall of cards. The output guides service rules, volunteer responsibilities, signage, intake forms, storage layout, and any future digital system. ## 1. Domain And Boundaries The service operates in the domain of shared community-tool stewardship. It helps neighborhood members access occasional-use tools, learn safe handling, and share the cost and responsibility of maintaining useful equipment. The main people and organizations are members, volunteer stewards, workshop facilitators, the neighborhood association, donors, and repair partners. It does not attempt to become a commercial equipment-rental company, lend high-risk professional machinery, or guarantee that every tool is always available. ## 2. Core Concepts And Relationships The core concepts are: - **Member:** a person eligible to borrow tools. - **Tool:** an individual lendable item with an identity, condition, location, and maintenance history. - **Tool type:** a category such as cordless drill, shovel, or stud finder. It is not an individual Tool. - **Loan:** the record of one Member borrowing one Tool for an agreed period. - **Condition check:** an inspection recorded before or after a Loan. - **Maintenance task:** work needed to keep a Tool safe and usable. - **Reservation:** a Member's request to borrow a Tool during a future period. - **Steward shift:** a scheduled period when a volunteer opens, closes, checks, or organizes the library. A Tool has one Tool type and may have many Loans, Condition checks, and Maintenance tasks. A Loan belongs to one Member and one Tool. A Tool cannot be loaned while an unresolved safety-related Maintenance task is open. ## 3. Rules, States, And Sources Of Truth Tool states are available, reserved, on loan, overdue, inspection needed, maintenance needed, and retired. A volunteer must record a Condition check when a Tool is returned. A Tool marked maintenance needed or retired cannot be loaned. For current possession, trust the active Loan record. For safety and usability, trust the latest Condition check and unresolved Maintenance tasks. For membership eligibility, trust the neighborhood association's current member list. If a card, spreadsheet, shelf label, and a person's memory conflict, pause the next Loan and reconcile the maintained record. ## 4. Actions, Automation, And Authority Members may request Reservations, borrow eligible Tools, report damage, and ask for help. Volunteer stewards may create Loans, record Condition checks, mark Tools unavailable, open Maintenance tasks, and waive a minor late return with a recorded reason. The treasurer may approve purchases and paid repairs inside the association's budget rules. Routine check-in, shelf organization, reminder notices, and availability updates may proceed without committee review when the maintained records are clear. Steward or treasurer approval is required before retiring a Tool, charging a Member, purchasing equipment, or returning a Tool to service after a safety-related repair. Any person handling a Loan must stop and defer when a Tool appears unsafe, identity or eligibility is unclear, or records conflict. No participant may lend a retired Tool or erase a damage or maintenance record to make a Tool appear available. ## Manual Workshop Outputs The workshop produces: - a shared vocabulary for signs, forms, storage labels, and volunteer training - a card-based relationship map for Tool, Loan, Condition check, and Maintenance task - a service blueprint covering reservation, pickup, return, inspection, repair, and retirement - a responsibility and authority table for members, stewards, the treasurer, and the association - a short list of records the service must maintain whether it uses paper, a spreadsheet, or future software ## What This Demonstrates Domain Context Modeling improves the service before any technology choice is made. It helps the group distinguish a Tool from a Tool type, connect availability to real condition and maintenance, clarify volunteer authority, and design a trustworthy borrowing experience. The same brief could later inform software or AI assistance, but neither is required for the framework to create value.