CollabKin
AI Story Drafts and Interview Questions
Designed to help the family prepare the next visit: a draft life story built from their own records, with the silent years marked and questions to ask the elder.
Industry solution
Oral histories, archives, congregations and festivals, working as one
Capture testimony with consent, license collections with care, keep dialogue respectful and run festival week without the scramble.

The problem
Heritage and faith organizations keep irreplaceable testimony, sensitive collections, busy congregations and festival crowds in separate spreadsheets, drives and group chats, run by a few staff and many volunteers.
Museums, archives, congregations and cultural associations hold things that cannot be replaced: a manuscript, a photograph of a rite, a founding family's letters, the trust of a community that lent them. Most of this work runs on a handful of staff and a larger circle of volunteers, with records spread across spreadsheets, shared drives, email and group chats. The archive is expected to be open and citable, yet some material is sacred or community-only, and donors' and narrators' wishes have to be honored long after the person who recorded them has moved on.
The generation that remembers the migrations, the first prayer halls and the early festivals is aging. Their testimony is often recorded by a grandchild on a phone, with the release form in a different place from the recording and the narrator's restrictions remembered by one volunteer. Reproduction requests, research visits and online discussion all draw on the same material, and each one is a chance to lose the community's confidence if the wrong image or the wrong claim goes out.
Public life adds its own pressure. Festivals, pilgrim visits and interfaith evenings bring crowds, questions in many languages and moments of tension when news breaks. Funders and trustees ask for evidence of what the year delivered. Each of these is handled in a different tool by different people, so the numbers, the rosters and the rules rarely meet.
Museum and archive directors
Protecting collections and community trust while growing public programs on a small staff and uncertain grant income.
Registrars and collections managers
Provenance, deeds of gift, access restrictions and reproduction requests handled consistently and on the record.
Oral history and community archive coordinators
Recordings, release forms, transcripts and narrator restrictions kept together before testimony is lost.
Faith community administrators
Congregations kept informed, volunteers organized and visitors briefed on customs, across generations and languages.
Diaspora and cultural association organizers
Passing traditions to the next generation and running festivals with volunteers spread across cities and group chats.
Development and grants managers
Evidence for funders and trustees that agrees, is traced to its source and takes hours to assemble, not a week.
A day in the life
Leena Varghese runs collections and community programs at Wrenfield Heritage Center, a small museum and archive founded by families who settled in the neighborhood over three generations. The center shares a street with a temple, a church, a mosque and a gurdwara, and every October it co-hosts the Lantern Walk, a multi-faith harvest festival that ends with lamps floated on the river. She has four staff, around 140 volunteers, a grant report due on Friday and the festival on Saturday.
Monday, 8:40 a.m.
Priya Abraham stops by with news: her grandfather Joseph, 91, finally talked about the crossing in 1962 and the first prayer hall the community rented above a laundromat. She recorded it at the kitchen table. Halfway through he asked that the part about his brother not be played in public while his sister-in-law is alive. The release form in the center's folder is an old version, the volunteer who arranged the interview has moved away, and three other families have emailed recordings with no forms at all.
How this is solved: Oral histories captured before they fade, with consent attachedMonday, 2:15 p.m.
A documentary producer asks to license the 1974 photograph of a coming-of-age ceremony for a series and needs an answer by Friday. Leena remembers that elders asked in 2019 that images of that rite be shown only to members, but the note is somewhere in email. The registrar finds two scans with different crops, no record of which one the center's own website used, and no trace of what the center charged the last time.
How this is solved: Sensitive collections and image reproduction requestsTuesday, 9:05 p.m.
News of vandalism at a place of worship across town is spreading. The center's interfaith discussion on what light means in each tradition, meant to lead into the festival, suddenly has forty new replies, some repeating a rumor that is not true. The youth circle is passing screenshots around, the three volunteer moderators are messaging each other on different apps, and the interfaith council's listening evening is on Thursday.
How this is solved: Keeping interfaith dialogue respectful when tensions riseWednesday, 6:30 p.m.
At the volunteer briefing Leena reconciles sign-ups from three group chats and a paper sheet pinned in the community hall. The kitchen needs twelve people for the evening meal, the procession needs sixteen marshals, and nobody has taken the accessibility desk during the procession. The hall performance has a fire-code capacity of 400, and last year's gate count was a guess written on a whiteboard.
How this is solved: Festival day: volunteers, stations and crowds on one planThursday, 11:00 a.m.
The front desk has fielded ninety calls and messages since Monday, in English, Malayalam, Spanish and Tagalog: can we take photos in the shrine room, is the procession wheelchair accessible, what should we wear, where do we park. A pilgrim group of thirty-eight wants a guided heritage walk that is already full, and a volunteer gave one caller the wrong procession time, which has now been forwarded around a group chat.
How this is solved: The same visitor and pilgrim questions, in many languagesFriday, 4:00 p.m.
The interim report on the regional heritage grant is due at five. The grant promised sixty oral histories, fifteen hundred digitized items and twelve public programs. Leena has attendance from four different sign-up tools, the digitization tally in the registrar's spreadsheet, volunteer hours on paper shift sheets, and a treasurer who wants the same figures, defined the same way, for Monday's board meeting.
How this is solved: Showing funders and trustees what the year deliveredNone of this is unusual for a heritage center; it is simply a week. The solution below shows how the same week could run with testimony captured under consent, reproduction requests routed to the people entitled to decide, dialogue moderated before it hardens, a festival staffed station by station, visitors answered from approved sources and a report that reads from the numbers the work already produced.
Challenges and how they are solved
Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.
Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.
Challenge 1 of 6
Joseph Abraham is 91 and has finally agreed to talk about the crossing and the first prayer hall. His granddaughter recorded two hours on her phone; the file lives on her laptop, the release form he signed is an older version filed in a folder at the center, and halfway through he asked that one passage about his brother stay private while his sister-in-law is alive. The volunteer who set up the interview has moved away, the transcript is half done, and three other families have emailed recordings with no release forms at all. Nobody can say with confidence what the archive is allowed to do with any of them.
Irreplaceable testimony sits on personal devices, restrictions a narrator asked for live only in someone's memory, and the archive cannot safely cite, play or share recordings it already holds.
A relative records a grandparent's stories in the family's private CollabKin space, naming the narrator and choosing who may see each story. When the family shares one, TheCulturePost is designed to keep it with its release form, who may hear it and any passage the narrator wants kept private, and to hold it until the form is signed. Staff can then cite it without guessing what the narrator agreed to.
Technical detail
Families start at home in CollabKin: a relative records a grandparent's stories into the family's private space, each with the narrator named and a visibility setting. CollabKin is designed to draft a life story from the family's own records, with the silent years marked and questions to ask at the next visit. When the family chooses to contribute a story, CollabKin is designed to hand it to TheCulturePost as a submission carrying the recording, the transcript draft, the narrator and the family's visibility choice. There, a consent and restriction register is designed to record which release form version was signed and witnessed, the access level the narrator chose, any withheld segments and the uses allowed, and to hold a recording until its form is signed. The oral history then enters the archive with narrator, language, transcript and access level, ready to cite, with its restrictions designed to travel with every citation.
Each recording is designed to arrive in the archive with its narrator, its signed release and its restrictions attached, so the center can cite it without guessing what the narrator agreed to.
CollabKin
Designed to help the family prepare the next visit: a draft life story built from their own records, with the silent years marked and questions to ask the elder.
TheCulturePost
Designed to keep each recording's release form, chosen access level and withheld segments together, including recordings contributed from a family's CollabKin space.
Works with CollabKin
TheCulturePost
The archive's oral history list: each recording with narrator, age, language and an access level such as Community or Members Only, ready to listen back and cite.
Challenge 2 of 6
On Monday afternoon a documentary producer asks to license a 1974 photograph of a coming-of-age ceremony and wants an answer by Friday. The print came with a deed of gift and a handwritten note, the scan has been reused on the center's own website, and the image shows a rite that elders asked in 2019 to be seen only by members. The registrar searches a spreadsheet for the deed of gift, the collections manager searches email for what the elders said, and nobody can tell which of two scans is the master or what the center charged the last time it licensed a photograph.
Community-restricted material risks leaving the community without consent, reproduction fees and credit lines are inconsistent, and a single mistaken release can cost years of trust with donor families.
TheCulturePost records where each item came from and who may see it, and ArtistryBase keeps every scan with the master copy marked. When a reproduction request arrives, ArtistryBase is designed to check who may see the item: public images go straight to fee and terms, while community-only and restricted images wait for the named cultural advisors' approval. Each license is recorded with its credit line and the exact copy released.
Technical detail
TheCulturePost holds the archive record: the photograph as an artifact with provenance, including the donor, rights notes and its access level, here community. ArtistryBase holds the digital surrogates as a work: every scan kept as an immutable numbered version, the master file typed as a master asset, and explicit license terms such as a one-time editorial license set on the work. When a reproduction request arrives, ArtistryBase's request desk is designed to read the item's access level from TheCulturePost. Public items move to fee and terms; community or restricted items open a review round with the named cultural advisors, and the license is designed to stay unissued until they sign off. The approved license, the credit line and the exact version released are recorded on the work, and the archive record in TheCulturePost is designed to show who reproduced the item and on what terms.
Every reproduction is designed to carry a traceable license, a credit line and the advisors' sign-off wherever the community asked for one, and the Friday answer comes from the record rather than memory.
TheCulturePost
The archive record every decision starts from: photographs, manuscripts, maps and objects filtered by kind and access level, each with provenance to check before it is cited or reproduced.
ArtistryBase
Designed to check each reproduction request against the item's access level in TheCulturePost and route community or restricted images to advisory sign-off before a license is issued.
Works with TheCulturePost, ComradeCircle
ArtistryBase
Explicit terms on the digital surrogate: license type, identifier such as CC-BY-4.0, price and attribution, set on the work that moves through review and approval before release.
Challenge 3 of 6
On Tuesday evening news of vandalism at a place of worship across town starts circulating. By nine o'clock the center's interfaith discussion on what light means in each tradition, planned as a lead-in to the festival, has forty new replies. Some are angry, a few repeat a rumor that is not true, and the youth circle is sharing screenshots. The three volunteer moderators are coordinating on different apps, the explainer everyone links to has no sources, and the interfaith council's listening evening is two days away.
Unmoderated threads harden into sides, rumor outruns fact, volunteer moderators burn out, and the goodwill that makes a shared multi-faith festival possible begins to fray.
Moderators hold new replies in TheCulturePost's interfaith discussion for review and flag the rumor. In the ComradeCircle youth group, each new post is designed to get a quick first check, so volunteer moderators see the likely rumor posts first and can overrule any verdict. They reply with a link to TheCulturePost's explainer, whose sources have been checked, and an announcement invites the youth group to Thursday's listening evening.
Technical detail
First, the forty replies sit in TheCulturePost's interfaith discussion, where every reply carries a moderation state (pending, approved, flagged or removed), so moderators hold new replies as pending and flag the rumor. Second, the screenshots are spreading in the youth circle on ComradeCircle, where moderation triage is designed to give each new post a first-pass verdict with a confidence score and its signals, escalating the rumor posts for a person to review or overturn. Third, the moderator answers each escalated post with a link to TheCulturePost's explainer, whose claim has passed citation review and is marked corroborated or disputed. Finally, a ComradeCircle announcement goes out to the youth circle with the discussion link and the invitation to Thursday's listening evening.
Moderators are designed to spend the evening on the handful of posts that need a person, while the conversation stays tied to sources rather than rumor.
ComradeCircle
Designed to give first-pass verdicts on posts in the youth circle, each with a confidence score and categories, so volunteer moderators see the rumor posts first and can overturn any verdict.
TheCulturePost
Holds the forty replies in the interfaith discussion, filtered by approved, pending, flagged and removed, with the discussion linked to the sourced story behind it.
TheCulturePost
The explainer moderators link to: each citation checked in editorial review and marked corroborated, disputed or retracted before the story is published.
Challenge 4 of 6
Festival staffing at a volunteer-run center follows the same pattern every year. Shift sign-ups live in three group chats and a paper sheet, skills such as first-aid certification are not recorded anywhere, and the hall's 400 limit is counted by a volunteer with a clicker. Gaps only show on the day: last year the accessibility desk stood empty for an hour during the procession, while two kitchen volunteers went home because nobody could say where they were needed. The schedule is rebuilt from scratch every October because last year's version lived on one organizer's phone.
Gaps surface on the day as unstaffed stations and long lines, hall capacity is managed by guesswork, and volunteers who came for a shift and felt unused do not come back next year.
Volunteers sign up for the briefing and each shift in one ComradeCircle group, where announcements reach everyone, including the approved festival poster from ArtistryBase. EventfullyManaged is designed to take that list, place each volunteer on a station and shift, show who holds first-aid certification and flag short-staffed stations while there is still time to ask the group. At the hall door, check-ins show when the hall reaches its 400 limit.
Technical detail
ComradeCircle runs the community side: a Festival Volunteers circle where members RSVP to the briefing, the setup day and each shift, and announcements reach everyone in one channel. ArtistryBase is designed to release the approved festival poster, drawn from the 1981 archive poster, to that announcements channel with its credit line. EventfullyManaged runs the festival as an event: the hall and its floor plan, the performance as a session capped at 400, free registrations and QR check-in at the gates and the hall door. Its volunteer station board is designed to take the roster from the ComradeCircle circle, place each volunteer on a station and shift, show first-aid certification against the stations that need it, and flag stations below minimum while there is still time to message the circle. On the day, session check-in is designed to tell the hall door when it reaches 400.
Every station is designed to have a named volunteer and a backup before the gates open, and hall capacity is read from check-ins rather than a clicker or a whiteboard guess.
ComradeCircle
The Festival Volunteers circle with its own channels: shift calls, the briefing time and the festival poster go out on the announcements channel, with RSVPs under the circle's Events tab.
EventfullyManaged
Designed to place every station and shift on the festival site plan, take the roster from the ComradeCircle volunteer circle and flag uncovered stations in time to fill them.
Works with ComradeCircle
Challenge 5 of 6
Every festival season the front desk answers the same few dozen questions by phone, email and messaging apps, in English, Malayalam, Spanish and Tagalog: photography in the shrine room, dress for each place of worship, wheelchair access on the procession route, parking by the river. The answers live in the heads of two part-time staff and on a printed sheet that still shows last year's start time. Walk bookings go into a notebook by the phone, so when a group leader asks for thirty-eight places nobody can see which dates have room, and a wrong time given once travels around group chats faster than anyone can correct it.
Staff spend festival week repeating answers, visitors receive inconsistent or wrong information, and sacred spaces welcome guests who were never told the customs they are expected to respect.
Botlit is designed to answer visitors on web chat and messaging apps, in their own language, using only material the center approves: the visitor guide, each congregation's agreed customs, the festival program from EventfullyManaged and checked explainers from TheCulturePost. It shows where each answer came from and passes anything it cannot answer to the front desk. Walk requests go to GGNomad, where group leaders can see dates and reserve places.
Technical detail
Botlit is designed to run the center's visitor and pilgrim assistant on web chat and messaging channels, answering only from knowledge bases the center approves: the visitor guide, the dress and photography customs agreed with each congregation, the festival program and route exported from EventfullyManaged, and sourced explainers from TheCulturePost. It is designed to reply in the visitor's language, show the passage behind each answer and, when nothing matches, say so and hand the conversation to the front desk. Questions about walks point to GGNomad, which is designed to list the center's guided heritage walks with dates, duration, difficulty and price, and to let a group leader reserve places for a bus tour group. Unmatched questions are gathered each week so staff can add what was missing.
Visitors are designed to get one consistent, sourced answer in their own language, and staff time goes to the questions that genuinely need a person.
Botlit
Designed to answer visitor and pilgrim questions in their language from approved sources, cite the passage, hand unmatched questions to staff and point bookings to GGNomad.
Works with TheCulturePost, EventfullyManaged, GGNomad
GGNomad
Where the center's guided heritage walks are designed to sit beside other local experiences, with duration, difficulty and price up front, so group leaders book instead of phoning.
Challenge 6 of 6
Grant reporting at a small heritage center is assembled by hand every time. Attendance sits in four sign-up tools that each count a returning visitor differently, the digitization tally lives in the registrar's spreadsheet, and volunteer hours are added up from paper shift sheets. Last year the interim report counted the festival from a gate estimate while the board pack counted wristbands, so the two documents disagreed and the treasurer spent the trustee meeting explaining why. Each deadline costs a day of reconciling numbers that should already agree, and the definitions change with whoever builds the spreadsheet.
Small teams lose days assembling numbers, figures disagree between the funder report and the board pack, and the next grant depends on evidence the organization cannot easily show.
Attendance from EventfullyManaged, archive counts from TheCulturePost and walk bookings from GGNomad are designed to come together in one BigConsole view that shows each grant deliverable against its target, with one agreed definition per measure. Every figure points back to where it came from. The treasurer and the funder's program officer get view-only access, so the grant report and the board pack use the same numbers.
Technical detail
EventfullyManaged holds the event-side evidence: registrations, check-ins by hour and session attendance for every program, with snapshots saved as each event closes. TheCulturePost holds the archive-side evidence: oral histories recorded, items described with provenance and an access level, and stories that passed citation review. GGNomad holds heritage walk bookings. These records are designed to land in keyed BigConsole data sinks through linked ingestion workflows, where a grant impact console shows each deliverable against its target with one agreed definition per measure, and an Explain panel is designed to cite the sink and field behind every statement. The console is shared view-only with the treasurer and with the funder's program officer, so the grant report and the board pack read from the same numbers.
Funder and board reports are designed to come from one shared view with every figure's source shown, so the Friday deadline becomes a review rather than a scramble.
BigConsole
Designed to show each grant deliverable against its target from EventfullyManaged, TheCulturePost and GGNomad data, with an Explain panel citing the source behind every figure.
Works with EventfullyManaged, TheCulturePost, GGNomad
EventfullyManaged
Registrations, check-ins and check-in throughput by hour, with saved snapshots, as the attendance evidence for each program and for festival day.
How it fits together
One year's cycle at a community heritage center, from a family recording at the kitchen table to the report the funder reads. Each step is one product doing one job and handing its output to the next.
To TheCulturePost: Stories the family chooses to share, with recording, draft transcript and narrator
To ArtistryBase: Where each requested item came from and who may see it
To ComradeCircle: The approved festival poster and its credit line, for community announcements
To EventfullyManaged: The volunteer list from the Festival Volunteers group
To Botlit: The festival program, route and times for the visitor assistant
To GGNomad: Visitors and group leaders ready to book a guided heritage walk
To BigConsole: Monthly walk bookings, alongside festival check-ins and archive counts
Step 1 of 8: Gather family memories
Technical detail
Products in this solution
Citable archive, oral histories and dialogue
Built for cultural storytelling where every claim has a source: an archive that records where each item came from and who may see it (public, community, restricted or closed until a set date), plus oral history recording and moderated interfaith discussion.
Technical detail
Built for citation-first cultural storytelling, a provenance-aware archive with public, community, restricted and embargoed access levels, oral history capture and moderated interfaith discussion.
Family memories and oral histories at home
A private, members-only family space where relatives record elders' stories and gather photos, naming each narrator and choosing who can see each story. It is designed to let a family share a chosen story with a community archive.
Technical detail
A private, members-only family space where relatives record elders' stories and gather photos, with narrators named and per-story visibility (whole tree, stewards only or private), and is designed to let a family contribute a chosen story to a community archive.
Scans, rights and reproductions
Keeps every scan as a numbered copy that is never overwritten, marks the master and the released version, runs reviews that end in a recorded approval, and sets clear license terms and a credit line on each work.
Technical detail
Keeps every scan as an immutable numbered version, with the master file typed as a master asset and the released version marked as published, runs review rounds that end in a recorded sign-off, and sets explicit license terms and attribution on each work.
Congregations, volunteers and community channels
Gives congregations, youth groups and volunteer teams their own groups, discussion channels, announcements and event sign-ups today, with a quick first check of new posts designed to help volunteer moderators spot the ones that need a person.
Technical detail
Gives congregations, youth groups and volunteer teams circles, channels, announcements and event RSVPs today, with moderation triage designed to help volunteer moderators.
Festival and public program operations
Runs festivals and public programs: venues and floor plans, sessions with capacity limits, QR check-in stations, separate access for staff and volunteers, and attendance reports saved as each event closes.
Technical detail
Runs festivals and public programs: venues and floor plans, sessions with capacity limits, check-in stations with QR scanning, role-scoped access for staff and volunteers, and attendance analytics with saved snapshots.
Heritage walks and visitor bookings
Brings tours and cultural experiences together with length, difficulty and price shown up front, and is designed to let the center list its guided heritage walks so visitors and group leaders can book them.
Technical detail
Brings tours and cultural experiences together with duration, difficulty and price up front, and is designed to let the center list its guided heritage walks so visitors and group leaders can book them.
Visitor and pilgrim assistant
Assistants that answer only from material you approve, designed to show where each answer came from, say so when that material has no answer and work on your website chat and messaging apps.
Technical detail
Governed agents grounded in approved knowledge bases, designed to cite passages, admit when nothing matches and deploy to web and messaging channels.
Funder and trustee reporting
Reports built from the records the organization already keeps, shared view-only with trustees, with an Explain panel designed to point to the source behind each statement.
Technical detail
Governed consoles built on keyed data sinks, with view-only sharing for trustees, and an Explain panel designed to cite the sink and field behind each statement.
All eight products run on Burdenoff Workspaces: one sign-on for staff, volunteers and advisors, role-based access that keeps community and restricted material with the people entitled to it, one audit trail across archive, rights, events and assistants, and one bill.
Concept gallery
15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.
CollabKin
Designed to help the family prepare the next visit: a draft life story built from their own records, with the silent years marked and questions to ask the elder.
TheCulturePost
Designed to keep each recording's release form, chosen access level and withheld segments together, including recordings contributed from a family's CollabKin space.
Works with CollabKin
TheCulturePost
The archive's oral history list: each recording with narrator, age, language and an access level such as Community or Members Only, ready to listen back and cite.
TheCulturePost
The archive record every decision starts from: photographs, manuscripts, maps and objects filtered by kind and access level, each with provenance to check before it is cited or reproduced.
ArtistryBase
Designed to check each reproduction request against the item's access level in TheCulturePost and route community or restricted images to advisory sign-off before a license is issued.
Works with TheCulturePost, ComradeCircle
ArtistryBase
Explicit terms on the digital surrogate: license type, identifier such as CC-BY-4.0, price and attribution, set on the work that moves through review and approval before release.
ComradeCircle
Designed to give first-pass verdicts on posts in the youth circle, each with a confidence score and categories, so volunteer moderators see the rumor posts first and can overturn any verdict.
TheCulturePost
Holds the forty replies in the interfaith discussion, filtered by approved, pending, flagged and removed, with the discussion linked to the sourced story behind it.
TheCulturePost
The explainer moderators link to: each citation checked in editorial review and marked corroborated, disputed or retracted before the story is published.
ComradeCircle
The Festival Volunteers circle with its own channels: shift calls, the briefing time and the festival poster go out on the announcements channel, with RSVPs under the circle's Events tab.
EventfullyManaged
Designed to place every station and shift on the festival site plan, take the roster from the ComradeCircle volunteer circle and flag uncovered stations in time to fill them.
Works with ComradeCircle
Botlit
Designed to answer visitor and pilgrim questions in their language from approved sources, cite the passage, hand unmatched questions to staff and point bookings to GGNomad.
Works with TheCulturePost, EventfullyManaged, GGNomad
GGNomad
Where the center's guided heritage walks are designed to sit beside other local experiences, with duration, difficulty and price up front, so group leaders book instead of phoning.
BigConsole
Designed to show each grant deliverable against its target from EventfullyManaged, TheCulturePost and GGNomad data, with an Explain panel citing the source behind every figure.
Works with EventfullyManaged, TheCulturePost, GGNomad
EventfullyManaged
Registrations, check-ins and check-in throughput by hour, with saved snapshots, as the attendance evidence for each program and for festival day.
Pitch kit
Heritage and faith organizations carry things that cannot be replaced: an elder's testimony, a photograph of a rite, a congregation's trust, a festival the whole neighborhood waits for. This solution concept brings eight Burdenoff products together so testimony can be captured with consent, collections licensed on the community's terms, dialogue kept respectful, festival week staffed station by station, visitors given sourced answers and funders shown cited results.
Questions
Yes. Every archive item and oral history in TheCulturePost carries a setting for who may see it, and ArtistryBase is designed to check that setting before any reproduction and send anything restricted to the advisors your community names. Those people always decide, and the products keep a record of what was decided and by whom.
Technical detail
That is the starting point of the design. Every archive item and oral history in TheCulturePost carries an access level (public, community, restricted or embargoed until a date), and the consent register is designed to keep the narrator's own restrictions beside the recording. Reproduction requests in ArtistryBase are designed to check that access level first and route anything restricted to the advisors your community names. The decision always stays with those people; the products keep the record of what was decided and by whom.
No. CollabKin is a private family space, and recordings, photos and stories stay there under the family's own settings. Sharing a story with the community archive is designed as a deliberate choice, made one story at a time, with the narrator and who may see it carried across.
Technical detail
No. CollabKin is a private, members-only family space, and a family's recordings, photos and stories stay there under the family's own roles and visibility settings. Contributing a story to the community archive is designed as a deliberate choice the family makes, one story at a time, with the narrator and visibility carried across.
It is designed not to. Botlit answers only from material you approve, such as your visitor guide, the customs each congregation has agreed and explainers whose sources have been checked, shows where each answer came from and passes the question to your staff when that material has no answer. Your team decides what the assistant may draw on.
Technical detail
Botlit agents are designed to answer only from knowledge bases you approve, such as your visitor guide, the customs each congregation has agreed and sourced explainers, and to show the passage behind each answer. When nothing matches, the assistant is designed to say so and hand the question to your staff rather than guessing. Your team decides what goes into those knowledge bases.
No. Many organizations would start with one pair, such as TheCulturePost and CollabKin for an oral history project, or ComradeCircle and EventfullyManaged for festival season, and add others later. Because all the products share one foundation, your people, their permissions and the record of who did what carry over.
Technical detail
No. Many organizations would start with one pair, for example TheCulturePost and CollabKin for an oral history project, or ComradeCircle and EventfullyManaged for festival season, and add others later. Because every product runs on the same Workspaces foundation, people, roles and the audit trail carry over when you add one.
Yes, that is the intent. The products are designed for several traditions and languages: perspective labels and moderation in interfaith discussions, each oral history marked with its language, and an assistant that replies in the visitor's language. Language coverage grows over time, so check the languages you need with us early.
Technical detail
The products are designed for multi-tradition and multilingual use: perspective labels and moderation in interfaith discussions, a language on every oral history, and an assistant designed to reply in the visitor's language from approved sources. Depth of language coverage grows over time, so it is worth checking the languages you need with us early.
No, not as described here. This page is a solution concept: the products are in early access or pre-launch, and several capabilities shown, including the new ideas on this page, describe how they are designed to work together rather than features you can switch on today. We would be glad to talk through which parts fit your organization first.
Technical detail
This page is a solution concept. The products involved are in early access or pre-launch, and several capabilities described here, including the new concepts, show how the products are designed to work together rather than features you can switch on today. We would be glad to talk through which parts fit your organization first.
Related domains
Challenges solved
How eight Burdenoff products are designed to work together for charities, member associations and their chapters, from gala night to funder report.
Challenges solved
How eight Burdenoff products are designed to work together for conference organizers, festival producers and meetup hosts, from ticket pacing to sponsor renewals.
Challenges solved
A solution concept that brings eight Burdenoff products together for schools, universities and bootcamps: early alerts, faster feedback, belonging, student services, proof of skill and focus.
Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.
This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.