Credit · member-only project

Your name on the framework — here’s how

The Human–AI Boundary Framework for Asset Management — to our knowledge the first of its kind for the sector — built from 2,796 community responses across four webinars (June–July 2026) and validated by you across three review cycles in August 2026 (11–14 · 17–21 · 24–28 Aug, whole-document final pass). Published as a living framework online plus a citable Version 1.0 snapshot, frozen 31 August 2026, with a Webinar 5 launch event to follow. It is community-developed guidance published by the Asset Management Council — practical guidance carrying the community's authority, not a formal standard.

The three tiers

TierWhoWhere your name appears
Co-developerWorking Group membersNamed on the framework's cover page and in the snapshot's front matter
ReviewerVolunteer reviewersNamed on the contributors page
Community contributorEvery webinar participantCollective acknowledgment (responses were anonymous and stay that way)

Step back at any time — the credit for cycles you contributed to stays. Credit follows participation, not attendance: answering the structured asks counts, and decisions close on the written log, not in the room.

The roster, live

Names appear here the moment someone confirms their RSVP — this list is read straight off the project.

Co-developers — the Working Group

Named on the framework's cover page and in the snapshot's front matter

Birendra Grewal · Fernan Abuid · Hema Wadhwa · Ivan Beirne · Kai Dong · Lalinda Karunaratne · Martin Boettcher · Oludolapo Olanrewaju · Rick Minato · Russell Bunn · Sardar Khan · Steven McCann · Susan Rebano-Edwards · Tim Davies · Titus Naidoo

Reviewers

Named on the contributors page

Birendra Grewal · Fernan Abuid · Kai Dong · Martin Boettcher · Sardar Khan · Tim Davies · Titus Naidoo

Community contributor: Collective acknowledgment (responses were anonymous and stay that way).

What it asks of you

Working Group: ~4½ hours total, all in August (budget 5) — 30-min kickoff (Tue 11) + two cycles of short asks (≤40 min) and one 60-min call each (Fri 14, Thu 20) + a ~45-min final read and vote (wk of 24 Aug). Reviewer: ~2 hours — two 1-hour case packets. This concentrates the advertised ≤4 h/month into one bigger month and ends two months early — the kickoff email asks you to confirm you can wear it; async-only participation on whatever you can give still counts and is still credited. One browser link; no new tools — everything happens in Fulcrum at /members/tasks. The Volunteer Code of Conduct you agreed to at signup applies throughout.

AMCouncil members join by confirming a short RSVP — role and August hours, under three minutes.

The AI-use statement (short form)

AI synthesises the community's 2,796 responses, drafts sections with line-by-line provenance, and compiles the disposition logs. Humans set direction, judge content, run the calls, sign the sections and own the outcome. The project itself runs under the framework it is producing: the AI's permissions are declared in advance, every action and refusal is logged, and the log is published. A full AI-use statement appears in the framework's front matter.

Ownership & licence: formal wording to follow — pending AMC sign-off (modelled on the W3C/IETF contributor-licence pattern). Until then, contribution terms are confirmed in the volunteer kickoff email.

Credit terms last updated 2026-08-08.