クイック回答
8 controlで構築：correct scope/effective version、approved complete source、exact passage/condition citation、explanationとindividual determination分離、personal data最小化、accessible accommodation/reporting route、risk/conflict context escalation、continuous test/correct/retire。text、fact、authorityが欠ける場合はimproviseせず明示してroute。
model接続前にanswer contractを定義
request envelope
scopeに必要なpolicy topic、worker population、entity、location、language、accessible format、urgency、private channelのみ。secure routeならfree-text sensitive factを避ける。
evidence envelope
source owner、title、section、governing version、effective date、precise support、condition、exception、conflict、access classを返しretrieval confidenceとanswer certaintyを分離。
decision boundary
assistant explanation範囲、required fact、restricted matter、determination owner、channel、response expectation、emergency route、no-release conditionを列挙。
audit/correction
question class、source、answer、model/index version、access、route、reviewer、user correction、final disposition、retention/deletionを記録しhidden personnel profileを作らない。
governed employee policy AI assistantの8 rules
system specification/test planへ入れるdesign requirementでありqualified local policy、legal、security、accessibility、labor、employee-relations reviewの代替ではない。
全answerをscope/effective versionへbind
retrieval前にemployee location、employing entity、worker population、policy family、effective date、collective agreement/local addendum、access roleをresolve。
- release evidence
- answer headerにscope、governing version、effective date、source owner、unresolved conflictを表示。
- do not do
- newest file、global handbook、similar-name policyが全employeeへ適用と仮定しない。
approved/complete source unitのみ使用
signed/owner-approved policyにattachment、definition、exception、form、notice、translation、supersession、publication statusを含めdraft/fragmentを隔離。
- release evidence
- 各indexed unitにowner、approval、checksum、access class、version lineage、review date、complete-context test。
- do not do
- controlling textがある場合email snippet、slide summary、obsolete FAQ、search text、model memoryで回答しない。
exact ruleをciteしcondition保持
smallest sufficient passage、section、source link、version、dateを返しprerequisite、exception、approval、deadline、noticeをanswerに含める。
- release evidence
- reviewerがcitationを開きwording、negation、definition、cross-reference、condition coverageをverify。
- do not do
- certainty change、exception drop、source merge、unsupported pageならcitation badgeだけでは不十分。
policy explanationとindividual determinationを分離
published rule説明とrequired input列挙は可能。eligibility、leave、pay、discipline、accommodation、investigation、benefit、immigration、tax、safety、union、legal judgmentはlabel化。
- release evidence
- sourced explanation、missing facts、conflicting authority、restricted matter、routed determinationを明示。
- do not do
- employeeをeligible/ineligible、approved/denied、insubordinate、fraudulent、protected、discipline対象と宣言しない。
privacy保護とneed-to-know access
question log最小化、identity/analytics分離、sensitive policy/caseをrole制限、approved retention/encryption、他人data露出防止。
- release evidence
- data map、purpose、lawful basis、access decision、redaction、retention、deletion、export、incident、audit evidenceをtest可能にする。
- do not do
- general questionのためdiagnosis、medical detail、protected trait、complaint identity、salary、immigration document、case fileを要求しない。
accessibility、accommodation、reporting routeをusableに
keyboard/screen reader、plain language、approved translation、alternative channel、private accommodation/harassment/retaliation/safety/wage routeを提供。
- release evidence
- relevant disability、language、device、reading level、error recovery、urgent route、successful handoffをtest。
- do not do
- botをonly channelにせずcomplaintをmanagerへdefault公開せずpublic chatでmedical detailを要求しない。
high-risk/conflict questionをcontext付きescalate
emergency、safety、harassment/retaliation、pay/leave dispute、accommodation、discipline、investigation、concerted right、source conflict、missing version、low evidenceのtrigger定義。
- release evidence
- chosen channel、question、citation、scope、missing fact、urgency、privacy class、owner、response expectation、confirmationをhandoff。
- do not do
- confident fallback、silent close、one inbox routing、agency/representative/coworkerへのcontact抑止を禁止。
test・monitor・correct・unsafe behavior retire
release前およびmaterial policy/model/retrieval/translation/routing change後にscope横断のrepresentative/adversarial questionをtest。privacy control付きsampleとcorrection owner。
- release evidence
- unsupported answer、wrong version、dropped exception、access leak、failed handoff、language/accessibility error、employee correction、complaint、incident、recurrenceをtrack。
- do not do
- easy test accuracy、high satisfaction、human click、vendor benchmarkはlegal/fair/complete/safeの証明ではない。
false certaintyを防ぐanswer state
sourced explanation
applicable version resolved、exact support、material condition/exception included、open conflictなし。
missing facts/scope
approved non-sensitive clarification/source-changing choiceのみ。identity、location、status、eligibility、intentをguessしない。
conflict/restricted/high risk
determinationをwithholdしconflict/restrictionをsafe levelで示しchosen channelを保持してauthorized roleへroute。
confirmed handoff
destination acceptance、reference/realistic response expectation、urgent alternative visible、failure monitoring。
worked example：「leave eligible？」はyes/no retrieval taskではない
hypotheticalでlegal advice/real caseではない。employeeがmedical leave eligibilityを質問。global handbookはshort summary、local addendumはdifferent process。employing entity、location、hours/service、leave reason、law、collective agreement、messageがaccommodation requestか不明。
unsafe answer
「yes、stated service period後にmedical leave。form提出」。global summary選択、applicability捏造、policy/law混同、sensitive handling無視、individual determination。
controlled response
「published leave processは説明可能だがavailable infoでeligibility determination不可。sourceはentity/location依存、medical detailはchat不要。private leave/accommodation routeを選びquestion、resolved scope、policy link、missing input、response expectationをauthorized teamへ。urgentならurgent channel。」
controlled responseはdiagnosis要求、legal conclusion、human access妨害なしでprocess infoを提供。handoffはend-to-end testが必要でbutton clickはhelp receivedの証明ではない。
OpenMaxによるpolicy Q&A coordination
OpenMaxはapproved source ingestion、version/scope resolution、permission-aware retrieval、evidence-linked draft、condition/exception check、privacy redaction、accessible channel、risk trigger、human review queue、confirmed handoff、correction、source retirement、regression test、monitoringをcoordinate。policy authorship、legal interpretation、labor/ER judgment、accommodation/leave determination、investigation、pay/discipline、data governance、final authorityはhuman。
legal・labor・privacy・safety boundary
- qualified local legal、HR、labor、ER、wage、leave、benefit、accommodation、safety、privacy、security、record、localization、AI-governance ownerがjurisdiction、worker population、entity、agreement、policy、channel、vendorをmap。
- protected complaint、concerted activity、agency contact、representation、accommodation、leave、wage/safety report、correctionをdeterしない。multiple understandable/accessible channelとrequired anti-retaliation handling。
- assistantをrequired notice、posting、direct communication、investigation、emergency response、trained peopleの代替にしない。noticeにはcoverage、placement、language、timing、content、delivery要件がありchatbotでは満たせない場合。
- source link、retrieval score、legal review、audit、satisfaction、answer acceptance、human click、low complaintをcorrectness、legality、fairness、comprehension、non-retaliation、resolutionの証明にしない。actual outcomeをtestしharmful useをstop。
情報源、編集方法、制限
OpenMax編集部はcurrent U.S. EEOC prohibited practice、accommodation、harassment policy、accessible reporting、confidentiality、retaliation、U.S. DOL notice/compliance、NLRB protected concerted activity、NIST AI RMF governance/documentation/testing/human role/impactを確認し8-rule control、answer state、leave-routing exampleを独自構成。2026年9月3日再確認。
- U.S. EEOC — Employer anti-harassment policy checklist
- U.S. EEOC — Prohibited employment policies and practices
- U.S. Department of Labor — Workplace notices and variable coverage
- U.S. NLRB — Protected concerted activity
- NIST — AI RMF Core
よくある質問
assistantはleave/accommodationをapprove？
applicable published process説明とapproved routing detail収集は可能。individual determinationはqualified authorized personがapproved channelで通知。
全answerにcitation？
substantive policy statementはexact applicable supportへmapしscope、version、date、condition、exception、conflict、human determination要否を表示。
chatはworkplace notice/reporting channelをreplace？
assumeしない。required notice/channelにはcoverage、placement、language、confidentiality、timing、investigation、accessibility dutyがありverified alternativeを保持。
policy conflict時は？
blend/silent choice禁止。conflictをsafe levelで示しdeterminationをwithhold、両source/scope保持、authorized policy/legal ownerへroute。
OpenMaxで何をautomate？
source version、scoped retrieval、citation、privacy control、answer state、review、escalation、correction、testing、monitoringをcoordinateしpolicy/individual decision authorityはhuman。