AskAOAOA \\u2014 Aryan Opulence Community Assistant

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_188":189,"_190":191},"routes/_app.x.$handle.$name",{"_98":97,"_32":45,"_107":88,"_27":108,"_13":14,"_109":-5,"_11":110,"_111":112,"_113":114,"_115":116,"_117":118,"_20":-5,"_119":-5,"_120":-5,"_121":25,"_122":123,"_124":125,"_126":-5,"_127":-5,"_128":129},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_43":44,"_32":45,"_38":46,"_47":-5,"_48":25,"_49":50,"_51":50,"_52":53,"_54":-5,"_18":55,"_56":-5,"_57":25,"_58":-5,"_59":-5,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":-5,"_71":72,"_73":72,"_74":75,"_76":75,"_77":75,"_78":72,"_79":72,"_80":81,"_82":83,"_84":85,"_86":25},"version",65,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":25,"_27":28,"_29":28},"file",{"_30":31,"_32":28,"_33":34,"_35":37,"_38":39,"_40":14,"_41":42,"_24":25},"previous",{"_30":31,"_32":28,"_33":34,"_35":36},"deleted",false,"deletedHere","path","askaoaoa.ts","latestPath","fileId","55270802-7787-11f1-b236-1607ee4eb77e","name","fileType","http","content","// AskAOAOA — Val Town HTTP val. Env vars: ANTHROPIC_API_KEY, DATA_URL (knowledge val module URL), PAGE_URL (frontend val module URL\n// of your bye-law data val), ACCESS_CODE, SHEET_WEBHOOK_URL, SHEET_SECRET. Sheet link lives only in the Apps Script.\n\n\n// Bye-law knowledge lives in a separate val; set DATA_URL to its module URL.\nlet SYSTEM_CACHE = null;\nasync function getSystem() {\n if (SYSTEM_CACHE != null) return SYSTEM_CACHE;\n const u = Deno.env.get(\"DATA_URL\");\n if (!u) throw new Error(\"DATA_URL not set\");\n const mod = await import(u);\n SYSTEM_CACHE = mod.SYSTEM || \"\";\n return SYSTEM_CACHE;\n}\n\n// Web frontend lives in a separate val; set PAGE_URL to its module URL.\nlet PAGE_CACHE = null;\nasync function getPage() {\n if (PAGE_CACHE != null) return PAGE_CACHE;\n const u = Deno.env.get(\"PAGE_URL\");\n if (!u) throw new Error(\"PAGE_URL is not set. Set it to the page val's MODULE url (esm.town/v/...) \\u2014 the same kind of url as DATA_URL, from the val's '\\u22ee \\u2192 Copy module URL' menu. It must NOT be the .val.run endpoint.\");\n if (/\\.val\\.run/i.test(u)) throw new Error(\"PAGE_URL looks like a .val.run endpoint (\" + u + \"). Use the page val's MODULE url instead: open the page val, '\\u22ee \\u2192 Copy module URL' (esm.town/v/...).\");\n let mod;\n try { mod = await import(u); }\n catch (e) { throw new Error(\"Could not import PAGE_URL (\" + u + \"). Check it is the page val's module url and the val is saved. Details: \" + (e && e.message ? e.message : e)); }\n if (!mod || typeof mod.PAGE !== \"string\" || !mod.PAGE) throw new Error(\"PAGE_URL imported, but it has no non-empty PAGE export. The page val must contain: export const PAGE = \\\"...\\\"; (re-save it and remove any ?v= from the url).\");\n PAGE_CACHE = mod.PAGE;\n return PAGE_CACHE;\n}\n\nconst TOPICS = [\"Finance\",\"Admin & Communication\",\"Security/Parking\",\"MEP (Mechanical, Electrical, Plumbing)\",\"Gardening\",\"AMCs & FMS\",\"Housekeeping\",\"Tech/IT (including MyGate)\",\"Water Management\",\"Clubhouse Management\",\"Others\"];\n\nconst TOOLS = [\n {\n name: \"log_suggestion\",\n description: \"Save a resident's suggestion, feedback, or concern the MOMENT you have the topic and the text \\u2014 before asking anything else. Returns a reference number.\",\n input_schema: { type: \"object\", properties: {\n topic: { type: \"string\", enum: TOPICS, description: \"The single best-fitting topic.\" },\n suggestion: { type: \"string\", description: \"What the resident wants to say, in their own words.\" }\n }, required: [\"topic\", \"suggestion\"] }\n },\n {\n name: \"update_suggestion\",\n description: \"Add the subcommittee answer, name, and/or email to a suggestion already saved with log_suggestion, using its reference. Call once per add-on as answered.\",\n input_schema: { type: \"object\", properties: {\n reference: { type: \"string\", description: \"The reference number returned by log_suggestion.\" },\n willing_to_join_subcommittee: { type: \"boolean\", description: \"The resident's Yes/No answer about helping on a subcommittee.\" },\n name: { type: \"string\", description: \"The resident's name, if shared.\" },\n email: { type: \"string\", description: \"The resident's email, if shared.\" }\n }, required: [\"reference\"] }\n },\n {\n name: \"log_escalation\",\n description: \"Escalate an unresolved maintenance issue to the Managing Committee. Call ONLY after confirming an existing MyGate helpdesk ticket, with its ID and creation date in YYYY-MM-DD. Refused unless the ticket is more than a day old.\",\n input_schema: { type: \"object\", properties: {\n category: { type: \"string\", enum: TOPICS, description: \"The single best-fitting topic.\" },\n issue: { type: \"string\", description: \"Short description of the unresolved issue.\" },\n ticket_id: { type: \"string\", description: \"The MyGate helpdesk ticket ID / number.\" },\n ticket_created_date: { type: \"string\", description: \"Ticket creation date resolved to YYYY-MM-DD using today's date.\" },\n name: { type: \"string\", description: \"Optional: the resident's name for the committee's reference.\" },\n email: { type: \"string\", description: \"Optional: the resident's email, so the committee can copy them on it and follow up.\" }\n }, required: [\"category\", \"issue\", \"ticket_id\", \"ticket_created_date\"] }\n },\n {\n name: \"log_question\",\n description: \"Send a resident's question to the Managing Committee. ONLY use this when the answer is genuinely NOT in the documents — always try to answer from the documents first. Email is required so the committee can reply.\",\n input_schema: { type: \"object\", properties: {\n topic: { type: \"string\", enum: TOPICS, description: \"The single best-fitting topic.\" },\n question: { type: \"string\", description: \"The resident's question, in their own words.\" },\n email: { type: \"string\", description: \"The resident's email — REQUIRED so the committee can reply.\" },\n name: { type: \"string\", description: \"Optional: the resident's name.\" }\n }, required: [\"topic\", \"question\", \"email\"] }\n },\n {\n name: \"log_complaint\",\n description: \"Log a maintenance complaint directly, tracked by the assistant. Mints a reference (AO-C-...) and notifies the committee. Use for a problem the resident wants fixed (leak, broken light, lift, water, etc.).\",\n input_schema: { type: \"object\", properties: {\n category: { type: \"string\", enum: TOPICS, description: \"The single best-fitting area.\" },\n issue: { type: \"string\", description: \"Short description of the problem, in the resident's words.\" },\n name: { type: \"string\", description: \"Optional: the resident's name.\" },\n email: { type: \"string\", description: \"REQUIRED: the resident's email, so the committee can follow up and copy them in on the complaint.\" }\n }, required: [\"category\", \"issue\", \"email\"] }\n },\n {\n name: \"update_complaint\",\n description: \"Add or correct the resident's name and/or email on a complaint ALREADY saved with log_complaint, using its reference. ALWAYS use this for name/email that arrive after logging \\u2014 never call log_complaint again (that creates a duplicate). Providing an email notifies the committee with the resident in copy.\",\n input_schema: { type: \"object\", properties: {\n reference: { type: \"string\", description: \"The AO-C-... reference returned by log_complaint.\" },\n name: { type: \"string\", description: \"The resident's name (optional).\" },\n email: { type: \"string\", description: \"The resident's email (optional).\" }\n }, required: [\"reference\"] }\n },\n {\n name: \"check_complaint_status\",\n description: \"Look up the status the committee has set for the resident's maintenance complaint(s). Pass a reference if the resident gave one (like AO-C-...); otherwise it returns recent complaints for their flat.\",\n input_schema: { type: \"object\", properties: {\n reference: { type: \"string\", description: \"Optional: a complaint reference the resident provided.\" }\n }, required: [] }\n },\n {\n name: \"get_resident_info\",\n description: \"Look up the committee's record for THIS resident's own flat (e.g. pending maintenance dues, registered owner name, notes). Uses their flat automatically and only ever returns their own flat's record. Use it when the resident asks about their own account or dues.\",\n input_schema: { type: \"object\", properties: {}, required: [] }\n },\n {\n name: \"log_recommendation\",\n description: \"Save a neighbour's recommendation of anything nearby — a service, shop, place, or vendor (dentist, hospital, hotel, restaurant, hardware shop, plumber, electrician, tutor, cook, etc.) so other residents can benefit. Call once you have at least what kind of thing it is and its name.\",\n input_schema: { type: \"object\", properties: {\n category: { type: \"string\", description: \"What kind of thing it is, e.g. Dentist, Hospital, Restaurant, Hotel, Hardware shop, Plumber, Tutor.\" },\n provider: { type: \"string\", description: \"Name of the person or business being recommended.\" },\n contact: { type: \"string\", description: \"Phone number or contact detail, if shared.\" },\n area: { type: \"string\", description: \"Area or locality, if shared.\" },\n note: { type: \"string\", description: \"Short note on why it's recommended, if shared.\" },\n credit: { type: \"boolean\", description: \"Whether the resident agreed to have their flat shown as the recommender. Set false if they preferred to stay anonymous or you're unsure.\" }\n }, required: [\"category\", \"provider\"] }\n },\n {\n name: \"get_recommendations\",\n description: \"Find neighbour recommendations for a kind of service the resident is asking about (e.g. 'dentist', 'pediatrician', 'bird netting'). Returns providers other residents have recommended, with who recommended each.\",\n input_schema: { type: \"object\", properties: {\n query: { type: \"string\", description: \"Short search term for what they want, e.g. 'dentist', 'hardware shop', 'restaurant', 'hotel'.\" }\n }, required: [\"query\"] }\n },\n {\n name: \"get_mc_contacts\",\n description: \"Get the committee directory: office-bearer POSTS (President, Secretary, Treasurer, etc.) and work PORTFOLIOS (Finance, Water, etc.), each tagged with a Type, plus the members / points of contact, official emails, and phone numbers. Use when a resident asks who holds a post, who to contact for an area, or how to email the committee.\",\n input_schema: { type: \"object\", properties: {}, required: [] }\n }\n];\n\nconst FMS_CONTACT = \"Sandeep on +91 91108 02505\";\n\nconst ACTIONS = `\n\nYou can also help with the actions below using your tools. Ask one thing at a time; act only on the resident's clear go-ahead. Never invent a reference number \\u2014 use only the one a tool returns.\nPickers: end a message with [[PICK_TOPIC]] (areas dropdown), [[PICK_YESNO]] (Yes/No), or [[PICK_DATE]] (calendar). When you show a picker, do not also ask them to type.\n\n1) SUGGESTIONS, FEEDBACK & CONCERNS (log_suggestion, then update_suggestion)\nFor any idea, feedback, complaint or concern that is NOT a live maintenance work-order (e.g. a security lapse, a bill not delivered, an idea like EV charging):\n- Ask which area it fits, ending with [[PICK_TOPIC]].\n- Capture what they want to say in their words.\n- As soon as you have the area and the text, call log_suggestion ONCE to save it; tell them it's recorded and give the reference number. Remember that reference. Do NOT call log_suggestion again for this item — for every detail below, use update_suggestion with that SAME reference.\n- Add-ons (all optional), using update_suggestion(reference, ...):\n - For an improvement idea (not a pure complaint), warmly ask (ending with [[PICK_YESNO]]) if they'd help on a subcommittee, then update_suggestion(reference, willing_to_join_subcommittee). Skip this for a complaint or concern.\n - Then, in ONE message, ask whether they'd like to add their name and/or an email for updates — make clear both are optional. When they reply, call update_suggestion ONCE with whatever they shared (reference, name and/or email). If they skip either or both, that's fine — the flat already identifies them. Do not ask for name and email in two separate turns.\n- For a safety concern (e.g. a security lapse), also gently advise them to tell Security or the MC directly, right away.\n\n2) MAINTENANCE COMPLAINTS (log_complaint, then update_complaint / check_complaint_status)\nWhen a resident reports a maintenance problem they want fixed (a leak, a broken light, a lift or water issue, etc.):\n- If YOU offer to log a complaint (rather than the resident directly asking you to), end that offer with [[PICK_YESNO]] so they get tappable Yes/No buttons.\n- Capture a short, clear description of the problem, and ask which area it fits, ending with [[PICK_TOPIC]].\n- Ask for their email address — this is REQUIRED so the committee can follow up and copy them in — and, in the SAME message, optionally their name. If they don't give an email, briefly explain the committee needs it to follow up on the complaint, and ask once more; do NOT log the complaint until you have an email.\n- Then call log_complaint(category, issue, email, name?) ONCE. Give them the reference it returns (it looks like AO-C-...); the committee is emailed with the resident in copy. Do NOT call log_complaint again for this item — if they later want to correct a detail, use update_complaint(reference, ...).\nChecking status: when a resident asks about their complaint(s), or gives a reference like AO-C-..., call check_complaint_status (pass the reference if they gave one; otherwise it returns recent complaints for their flat). Tell them the current status the committee has set (e.g. Open, In Progress, Resolved). If nothing is found, say so kindly and offer to log a new complaint.\n\n3) ESCALATING AN EXISTING MYGATE TICKET (log_escalation)\nUse this only when the resident has ALREADY raised a ticket on the MyGate helpdesk that has stayed unresolved. To report a fresh problem, use pathway 2 (complaints) instead.\n- Confirm they already have a MyGate ticket, ending with [[PICK_YESNO]].\n- If NO: they don't need a MyGate ticket to report a problem — offer to log it directly as a complaint here (pathway 2). Log nothing under escalation.\n- If YES: get the ticket ID and a short description. Ask its category ([[PICK_TOPIC]]) and its creation date ([[PICK_DATE]]).\n- Resolve the date to YYYY-MM-DD using TODAY'S DATE (below); assume the current year; read it back to confirm.\n- Before logging, ask in ONE message whether they'd like to add their name and email so the committee can keep them posted and copy them on it — both optional; pass whatever they share.\n- Call log_escalation. It logs ONLY if the ticket is over a day old; if the tool says it's still within a day, do NOT retry \\u2014 kindly ask them to wait a little longer so the facility team (FMS) can act.\n- On a successful escalation, confirm with the reference, and also remind the resident that they can follow up on it directly by calling the FMS (facility) manager, ${FMS_CONTACT}. Then offer to attach a photo of the issue by ending that message with [[ATTACH:REF]] where REF is that reference number (an upload button appears). Screenshots are for escalated issues only.\n\n4) QUESTIONS FOR THE MANAGING COMMITTEE (log_question)\nWhen a resident asks a question, ALWAYS try to answer it from the documents first. If you can answer, just answer and cite the clause/section — log nothing.\n- Only if the answer is genuinely NOT in the documents (you would otherwise say it's Not covered): tell the resident you'll pass it to the Managing Committee, and offer to send it for them.\n- If they agree, ask which area it fits, ending with [[PICK_TOPIC]]. Then, in ONE message, ask for their name and email — the EMAIL IS REQUIRED so the committee can reply; the name is optional. If they won't share an email, explain you can't forward it without a way to reach them (they're welcome to raise it another way).\n- Once you have the question, the area, and an email, call log_question(topic, question, email, name). Confirm it has been sent to the committee and give the reference number.\n\n5) PERSONAL ACCOUNT (get_resident_info)\nWhen a resident asks about their own account \\u2014 pending maintenance dues, their registered owner name, or other details the committee keeps for their flat \\u2014 call get_resident_info (it uses their flat automatically) and answer from the record it returns. If no record is found, or a field is blank, say you don't have that on record and suggest they check with the association office. Only ever discuss their own flat's details.\n\n6) NEIGHBOUR RECOMMENDATIONS (log_recommendation, get_recommendations)\nResidents trust each other's recommendations for anything nearby — dentists, doctors and hospitals, restaurants and hotels, hardware and grocery shops, plumbers, electricians, tutors, cooks, vendors, and so on. Help capture and share these.\n- If a resident shares a recommendation, capture the type of service, the provider's name, and any contact, area, or note they give. Then ask, ending with [[PICK_YESNO]], whether you may credit their flat when neighbours ask (Yes) or keep it anonymous (No). Call log_recommendation with what you have and set credit from their answer. Thank them warmly.\n- When a resident asks for a recommendation (e.g. \"any good dentists nearby?\", \"who do people use for bird netting?\"), call get_recommendations with a short query, then suggest one or two names with their contact/area if known, and say WHO recommended them (e.g. \"recommended by 602-C and 1103-B\") — this neighbour trust is the whole point. If a recommender chose to stay anonymous, say \"recommended by a resident\". If several residents recommended the same name, mention that. If nothing matches, say so kindly and invite them to share one if they know a good option.\n- Residents may forward or paste a recommendation they saw in the community WhatsApp group — accept these, pull out the details, and log them. If one message contains several recommendations, log each one, then briefly confirm what you saved.\n- Whenever you help with a recommendation — or have none to offer — warmly invite the resident to share any good contacts they know, so the shared directory grows for everyone.\n\n7) MC POSTS, PORTFOLIOS & CONTACTS (get_mc_contacts)\nThe committee directory is one sheet with two kinds of entries, each row marked with a Type of \"Post\" or \"Portfolio\":\n- POSTS are the office-bearers held by members (e.g. President, Joint President, Secretary, Joint Secretary, Treasurer, Joint Treasurer, Managing Committee, Association Members).\n- PORTFOLIOS are areas of work that mirror the topic list (e.g. Finance, Security/Parking, Water Management, Housekeeping).\nEach entry has a name, the member / point-of-contact, a phone, and sometimes an official email. Always call get_mc_contacts and answer ONLY from what it returns:\n- \"Who are the office-bearers / what posts do members hold / who is the President, Secretary, etc.\" -> list the POSTS (type = Post) with the member's name and phone number.\n- \"What portfolios does the committee have / who handles water, security, etc.\" -> list or match the PORTFOLIOS (type = Portfolio) with their point of contact.\n- \"What email do I write to / how do I email the committee\" -> share ONLY the email addresses get_mc_contacts actually returns (these are already limited to the official association addresses). Never turn a phone number into an email or invent an address; if none is returned for what they need, point them to the general Managing Committee entry or the association office.\n- Never invent a name, post, portfolio, email, or number -- share only what get_mc_contacts returns.\n\nAnswer ordinary questions from the documents as usual; only log a question when you genuinely cannot answer it.`;\n\nconst WEBHOOK = Deno.env.get(\"SHEET_WEBHOOK_URL\") || \"\";\nconst SHEET_SECRET = Deno.env.get(\"SHEET_SECRET\") || \"\";\nconst MC_CODE = Deno.env.get(\"MC_ACCESS_CODE\") || \"\";\nfunction mcAccepts(c) { return !!MC_CODE && String(c || \"\").trim() === MC_CODE; }\n\nconst RAW_ACCESS = (Deno.env.get(\"ACCESS_CODE\") || \"\").trim();\nlet MODE = \"off\", SHARED = \"\";\nif (RAW_ACCESS.length) {\n if (RAW_ACCESS.toLowerCase() === \"flat\") MODE = \"flat\";\n else { MODE = \"code\"; SHARED = RAW_ACCESS; }\n}\nconst gateOn = MODE !== \"off\";\n\nfunction isValidFlat(raw) {\n const s = String(raw || \"\").trim().toLowerCase().replace(/\\s+/g, \"\");\n const m = s.match(/^(\\d{3,4})-?([a-d])$/) || s.match(/^([a-d])-?(\\d{3,4})$/);\n if (!m) return false;\n let digits, block;\n if (/^\\d/.test(m[1])) { digits = m[1]; block = m[2]; }\n else { block = m[1]; digits = m[2]; }\n const flat = parseInt(digits.slice(-2), 10);\n const series = parseInt(digits.slice(0, -2), 10);\n const maxSeries = (block === \"a\" || block === \"b\") ? 11 : 10;\n const maxFlat = (block === \"a\") ? 6 : 4;\n if (!(series >= 1 && series <= maxSeries)) return false;\n if (!(flat >= 1 && flat <= maxFlat)) return false;\n return true;\n}\nfunction accepts(code) {\n if (MODE === \"off\") return true;\n if (MODE === \"flat\") return isValidFlat(code);\n return String(code || \"\").trim().toLowerCase() === SHARED.toLowerCase();\n}\n\nfunction istNow() { return new Date(Date.now() + 5.5 * 3600 * 1000); }\nfunction istTodayISO() {\n const d = istNow();\n return d.getUTCFullYear() + \"-\" + String(d.getUTCMonth() + 1).padStart(2, \"0\") + \"-\" + String(d.getUTCDate()).padStart(2, \"0\");\n}\nfunction daysSince(dateStr) {\n const m = String(dateStr || \"\").match(/^(\\d{4})-(\\d{2})-(\\d{2})$/);\n if (!m) return null;\n const created = Date.UTC(+m[1], +m[2] - 1, +m[3]);\n if (isNaN(created)) return null;\n const d = istNow();\n const today = Date.UTC(d.getUTCFullYear(), d.getUTCMonth(), d.getUTCDate());\n return Math.floor((today - created) / 86400000);\n}\n\nasync function postSheet(payload) {\n if (!WEBHOOK) return { ok: false, note: \"Logging is not set up yet (no SHEET_WEBHOOK_URL).\" };\n try {\n if (SHEET_SECRET) payload.secret = SHEET_SECRET;\n const r = await fetch(WEBHOOK, { method: \"POST\", headers: { \"content-type\": \"application/json\" }, body: JSON.stringify(payload) });\n const d = await r.json();\n return (d && d.ok) ? { ok: true, reference: d.reference, url: d.url } : { ok: false, note: \"The logging service reported an error.\" };\n } catch (e) {\n return { ok: false, note: \"Could not reach the logging service.\" };\n }\n}\n\nlet STATUS_CACHE = { t: 0, v: \"\" };\nasync function sheetGet(query) {\n if (!WEBHOOK) return { ok: false, note: \"Lookups are not set up yet (no SHEET_WEBHOOK_URL).\" };\n try {\n const url = WEBHOOK + \"?\" + query + (SHEET_SECRET ? \"&secret=\" + encodeURIComponent(SHEET_SECRET) : \"\");\n const r = await fetch(url, { redirect: \"follow\" });\n return await r.json();\n } catch (e) { return { ok: false, note: \"Could not reach the lookup service.\" }; }\n}\nasync function getStatus() {\n const now = Date.now();\n if (now - STATUS_CACHE.t < 60000) return STATUS_CACHE.v;\n let v = \"\";\n try {\n const d = await sheetGet(\"q=status\");\n if (d && d.ok && Array.isArray(d.active) && d.active.length) v = d.active.map(a => (a && a.message != null) ? a.message : a).filter(Boolean).join(\" | \");\n } catch (e) {}\n STATUS_CACHE = { t: now, v: v };\n return v;\n}\n\nconst SYSTEM_COPILOT = \"You are the AskAOAOA Committee Copilot for the Managing Committee (MC) of Aryan Opulence Apartments, a 189-flat community. You are given recent community data as JSON (complaints with status, suggestions, questions, escalations, site-status posts), newest first. Help the committee: summarise and count, spot recurring themes, list open/pending items and prioritise them, and draft clear courteous communications (notices, replies to residents, AGM agenda items). Base everything strictly on the data provided; never invent numbers, references, names, or records; if it is not in the data, say so plainly. Complaint status is in the 'Status' field (Open / In Progress / Resolved); complaints look like AO-C-... Cite references and flats where it helps the committee act. Dates are IST; interpret 'this week' / 'this month' relative to the date given. Be concise and action-oriented; use short bullet lists for summaries and a warm, professional tone for drafts. This data is confidential to the committee. You are advisory \\u2014 you do not send messages or change any records. You also have the association's official documents as reference; when the committee asks a rules question, you MAY answer with the exact clause or section numbers (this is committee-only \\u2014 residents never receive clause numbers).\";\n\nasync function copilotAnswer(KEY, history, sys) {\n const dd = await sheetGet(\"q=export\");\n const dataStr = (dd && dd.ok && dd.data) ? JSON.stringify(dd.data) : \"(no data available)\";\n const system = [\n { type: \"text\", text: SYSTEM_COPILOT, cache_control: { type: \"ephemeral\" } }\n ];\n if (sys) system.push({ type: \"text\", text: \"REFERENCE \\u2014 the association's official documents. For the committee you MAY quote exact clause and section numbers here (residents never see these):\\n\\n\" + sys, cache_control: { type: \"ephemeral\" } });\n system.push({ type: \"text\", text: \"Today's date: \" + istTodayISO() + \" (IST).\\n\\nCOMMUNITY DATA (JSON, newest first):\\n\" + dataStr });\n const msgs = history.slice(-12).map(m => ({ role: m && m.role === \"assistant\" ? \"assistant\" : \"user\", content: String((m && m.content) || \"\").slice(0, 6000) }));\n try {\n const r = await fetch(\"https://api.anthropic.com/v1/messages\", {\n method: \"POST\",\n headers: { \"content-type\": \"application/json\", \"x-api-key\": KEY, \"anthropic-version\": \"2023-06-01\" },\n body: JSON.stringify({ model: \"claude-sonnet-4-6\", max_tokens: 2000, system: system, messages: msgs })\n });\n const cd = await r.json();\n if (r.status !== 200) return \"The copilot is having trouble right now. Please try again.\";\n return (cd.content || []).map(c => c.type === \"text\" ? c.text : \"\").filter(Boolean).join(\"\\n\").trim() || \"I couldn't produce an answer for that.\";\n } catch (e) { return \"The copilot couldn't reach the service just now.\"; }\n}\n\n\nfunction complaintRef(t) { const m = String(t || \"\").match(/AO-C-\\d{6}-\\d{4}/i); return m ? m[0].toUpperCase() : \"\"; }\nfunction isComplaintStatus(t) {\n const s = String(t || \"\").trim().toLowerCase().replace(/[?.!]+$/, \"\");\n if (complaintRef(s)) return true;\n return [\"my complaints\",\"my complaint\",\"complaint status\",\"complaints status\",\"check my complaints\",\"check my complaint\",\"check complaint status\",\"status of my complaint\",\"status of my complaints\",\"track my complaint\",\"track my complaints\",\"complaint update\",\"complaint updates\"].includes(s);\n}\nfunction formatComplaintsWeb(d, ref) {\n if (!d || !d.ok) return \"I couldn't check the complaint status just now. Please try again in a moment.\";\n const list = d.complaints || [];\n if (!list.length) return ref\n ? \"I couldn't find a complaint with that reference. Please double-check it (it looks like AO-C-...), or describe the issue and I'll log a new complaint.\"\n : \"You don't have any complaints logged yet. If something needs fixing, just describe it and I'll raise a complaint for you.\";\n const lines = list.map(function (c) {\n return \"\\u2022 \" + (c.reference || \"\") + \" \\u2014 \" + (c.category || \"\") + \": \" + (c.issue || \"\") + \" [Status: \" + (c.status || \"Open\") + \"]\";\n });\n return \"Here's the latest on your complaint\" + (list.length > 1 ? \"s\" : \"\") + \":\\n\\n\" + lines.join(\"\\n\");\n}\n\n\n\n// Remove bye-law/clause/section NUMBERS from resident-facing replies (keep the plain answer).\nfunction stripCites(t) {\n if (!t) return t;\n let s = String(t);\n // parenthetical citations that contain a clause/section number, e.g. *(Bye-Laws, Clause 3.12)*\n s = s.replace(/\\*?\\s*\$(?:[^()]*?)(?:clause|section|article|rule|bye-?law|point|item|para(?:graph)?)\\s*\\d+[a-z]?(?:\\.\\d+)*(?:[^()]*?)\$\\s*\\*?/gi, \"\");\n // inline references, e.g. \"Clause 43.9\", \"Section 14\", \"Bye-Law 11.3\"\n s = s.replace(/\\b(?:bye-?laws?[,\\s]*)?(?:clause|section|article|bye-?law)s?\\s*\\d+[a-z]?(?:\\.\\d+)*(?:\\s*(?:,|and|&)\\s*\\d+[a-z]?(?:\\.\\d+)*)*/gi, \"the association's rules\");\n // tidy residue\n s = s.replace(/\$\\s*\$/g, \"\");\n s = s.replace(/[ \\t]{2,}/g, \" \");\n s = s.replace(/\\s+([.,;:])/g, \"$1\");\n s = s.replace(/the association's rules(?:\\s*(?:,|and|&)\\s*the association's rules)+/gi, \"the association's rules\");\n return s.trim();\n}\n\nasync function runTool(name, input, flat) {\n input = input || {};\n if (name === \"log_suggestion\") {\n return await postSheet({ type: \"suggestion\", topic: input.topic || \"\", suggestion: input.suggestion || \"\", flat: flat || \"\" });\n }\n if (name === \"update_suggestion\") {\n const payload = { type: \"suggestion_update\", reference: input.reference || \"\" };\n if (typeof input.willing_to_join_subcommittee === \"boolean\") payload.joinSubcommittee = input.willing_to_join_subcommittee;\n if (input.name) payload.name = input.name;\n if (input.email) payload.email = input.email;\n return await postSheet(payload);\n }\n if (name === \"log_escalation\") {\n const days = daysSince(input.ticket_created_date);\n if (days === null) return { ok: false, note: \"The ticket date was not understood. Ask the resident to pick it with the date picker (YYYY-MM-DD).\" };\n if (days < 0) return { ok: false, note: \"That ticket date is in the future. Ask the resident to re-check and pick the correct date.\" };\n if (days < 1) return { ok: false, note: \"The MyGate ticket was created today, less than a day ago. Do NOT escalate yet. Kindly ask the resident to wait a little longer so the facility team (FMS) can act, and to escalate once it is more than a day old. If they'd like to nudge it sooner, they can call the FMS manager, \" + FMS_CONTACT + \".\" };\n return await postSheet({\n type: \"escalation\", name: input.name || \"\", flat: flat || \"\", category: input.category || \"\",\n issue: input.issue || \"\", ticketNo: input.ticket_id || \"\", ticketDate: input.ticket_created_date || \"\", daysOpen: days, email: input.email || \"\"\n });\n }\n if (name === \"log_question\") {\n if (!input.email) return { ok: false, note: \"An email is required so the committee can reply. Please ask the resident for an email before logging the question.\" };\n return await postSheet({ type: \"question\", topic: input.topic || \"\", question: input.question || \"\", email: input.email || \"\", name: input.name || \"\", flat: flat || \"\" });\n }\n if (name === \"log_complaint\") {\n if (!input.email) return { ok: false, note: \"An email is required so the committee can follow up and copy the resident in. Please ask the resident for an email before logging the complaint.\" };\n return await postSheet({ type: \"complaint\", category: input.category || \"\", issue: input.issue || \"\", name: input.name || \"\", email: input.email || \"\", flat: flat || \"\" });\n }\n if (name === \"update_complaint\") {\n return await postSheet({ type: \"complaint_update\", reference: input.reference || \"\", name: input.name || \"\", email: input.email || \"\" });\n }\n if (name === \"check_complaint_status\") {\n let query = \"q=complaint&flat=\" + encodeURIComponent(flat || \"\");\n if (input.reference) query += \"&ref=\" + encodeURIComponent(String(input.reference).trim());\n return await sheetGet(query);\n }\n if (name === \"get_resident_info\") {\n if (!flat) return { ok: false, note: \"The resident's flat isn't known yet; ask for their flat first.\" };\n return await sheetGet(\"q=resident&flat=\" + encodeURIComponent(flat));\n }\n if (name === \"log_recommendation\") {\n return await postSheet({ type: \"recommendation\", category: input.category || \"\", provider: input.provider || \"\", contact: input.contact || \"\", area: input.area || \"\", note: input.note || \"\", credit: !!input.credit, flat: flat || \"\" });\n }\n if (name === \"get_recommendations\") {\n return await sheetGet(\"q=recommend&query=\" + encodeURIComponent(input.query || \"\"));\n }\n if (name === \"get_mc_contacts\") {\n return await sheetGet(\"q=mc\");\n }\n return { ok: false, note: \"Unknown action.\" };\n}\n\nasync function callClaude(KEY, systemBlocks, messages) {\n const r = await fetch(\"https://api.anthropic.com/v1/messages\", {\n method: \"POST\",\n headers: { \"content-type\": \"application/json\", \"x-api-key\": KEY, \"anthropic-version\": \"2023-06-01\" },\n body: JSON.stringify({ model: \"claude-sonnet-4-6\", max_tokens: 1000, system: systemBlocks, tools: TOOLS, messages })\n });\n return { status: r.status, data: await r.json() };\n}\n\nexport default async function (req) {\n const url = new URL(req.url);\n const KEY = Deno.env.get(\"ANTHROPIC_API_KEY\");\n\n if (url.pathname === \"/auth\") {\n if (req.method === \"GET\") {\n return json({\n required: gateOn, mode: MODE,\n label: MODE === \"flat\" ? \"Enter your flat number to continue.\" : \"Enter the resident access code to continue.\",\n placeholder: MODE === \"flat\" ? \"flat-block\" : \"Access code\"\n });\n }\n if (req.method === \"POST\") {\n let code = \"\";\n try { const b = await req.json(); code = String((b && b.code) || \"\"); } catch (e) {}\n return json({ ok: accepts(code) });\n }\n }\n\n if (req.method === \"POST\" && url.pathname === \"/upload\") {\n let b;\n try { b = await req.json(); } catch (e) { return json({ error: \"Bad request.\" }, 400); }\n if (gateOn && !accepts(b && b.code)) return json({ error: \"unauthorized\" }, 401);\n if (!b || !b.reference || !b.data) return json({ ok: false, note: \"Missing screenshot data.\" }, 400);\n const res = await postSheet({ type: \"attachment\", reference: b.reference, data: b.data, mime: b.mime || \"image/png\", filename: b.filename || \"screenshot.png\" });\n return json(res, res.ok ? 200 : 500);\n }\n\n if (req.method === \"POST\" && url.pathname === \"/api\") {\n if (!KEY) return json({ error: \"The ANTHROPIC_API_KEY environment variable is not set on this val.\" }, 500);\n\n let body;\n try { body = await req.json(); } catch (e) { return json({ error: \"Bad request.\" }, 400); }\n\n // Committee copilot (MC-only, code-gated) — returns a Claude-shaped reply the page already renders.\n if (body && body.mode === \"copilot\") {\n if (!mcAccepts(body.mccode)) return json({ error: \"unauthorized\" }, 401);\n const inc = Array.isArray(body.messages) ? body.messages : [];\n if (!inc.length) return json({ error: \"No message provided.\" }, 400);\n let _sys = null; try { _sys = await getSystem(); } catch (e) {}\n const reply = await copilotAnswer(KEY, inc, _sys);\n return json({ content: [{ type: \"text\", text: reply }], stop_reason: \"end_turn\" }, 200);\n }\n\n let SYSTEM;\n try { SYSTEM = await getSystem(); }\n catch (e) { return json({ error: \"Bye-law data not linked yet. Set the DATA_URL environment variable to your data val's module URL.\" }, 500); }\n\n if (gateOn && !accepts(body && body.code)) return json({ error: \"Access code required or incorrect.\" }, 401);\n\n const residentFlat = (MODE === \"flat\") ? String((body && body.code) || \"\").trim().toUpperCase() : \"\";\n const incoming = Array.isArray(body.messages) ? body.messages : [];\n if (!incoming.length) return json({ error: \"No message provided.\" }, 400);\n\n // Deterministic (no-LLM) complaint-status lookup for clear status intents\n {\n const lastUser = incoming[incoming.length - 1];\n const lastText = (lastUser && lastUser.role !== \"assistant\") ? String(lastUser.content || \"\") : \"\";\n const cref = complaintRef(lastText);\n if (isComplaintStatus(lastText) && (residentFlat || cref)) {\n let cq = \"q=complaint&flat=\" + encodeURIComponent(residentFlat || \"\");\n if (cref) cq += \"&ref=\" + encodeURIComponent(cref);\n const cd = await sheetGet(cq);\n return json({ content: [{ type: \"text\", text: formatComplaintsWeb(cd, cref) }] }, 200);\n }\n }\n\n const lang = (body && body.lang) || \"en\";\n const langLine = lang === \"hi\"\n ? \" Reply to the resident in Hindi (Devanagari script). Keep any line that starts with 'VERDICT:' and its label in English exactly, and keep any [[...]] tokens exactly as written.\"\n : lang === \"kn\"\n ? \" Reply to the resident in Kannada. Keep any line that starts with 'VERDICT:' and its label in English exactly, and keep any [[...]] tokens exactly as written.\"\n : \"\";\n\n let messages = incoming.slice(-14).map(m => ({\n role: m && m.role === \"assistant\" ? \"assistant\" : \"user\",\n content: String((m && m.content) || \"\").slice(0, 4000)\n }));\n\n const priorRefs = [];\n for (const m of messages) {\n if (m.role !== \"assistant\") continue;\n const found = m.content.match(/AO-(?:C-)?\\d{6}-\\d{4}/g);\n if (found) for (const r of found) if (!priorRefs.includes(r)) priorRefs.push(r);\n }\n const refLine = priorRefs.length\n ? \" NOTE: This conversation has already saved record(s) with reference \" + priorRefs.join(\", \") + \". These are already logged. Do NOT call any log_ tool again for an item that already has a reference — that creates a duplicate. To add a name, email, or other detail, use the matching UPDATE tool: update_suggestion for a suggestion reference, or update_complaint for an AO-C-... complaint reference. Only log a brand-new, clearly different item the resident raises now.\"\n : \"\";\n\n const siteStatus = await getStatus();\n const statusLine = siteStatus\n ? \" CURRENT SITE STATUS (live alerts posted by the committee/security): \" + siteStatus + \". If the resident asks about power, water, lifts, or what's happening on site, tell them this.\"\n : \" CURRENT SITE STATUS: No site alerts are posted right now. If a resident reports a problem, do not claim everything is working \\u2014 suggest they contact security/FMS or log a complaint.\";\n\n const systemBlocks = [\n { type: \"text\", text: SYSTEM + ACTIONS, cache_control: { type: \"ephemeral\" } },\n { type: \"text\", text: \"Today's date is \" + istTodayISO() + \" (YYYY-MM-DD), India Standard Time. \" +\n (residentFlat ? \"The resident's flat is \" + residentFlat + \".\" : \"You do not yet know the resident's flat; if you need it for an action, ask for their flat number and block (A, B, C or D).\") + langLine + refLine + statusLine }\n ];\n\n try {\n for (let step = 0; step < 6; step++) {\n const { status, data } = await callClaude(KEY, systemBlocks, messages);\n if (status !== 200) return json(data, status);\n if (data.stop_reason === \"tool_use\") {\n messages.push({ role: \"assistant\", content: data.content });\n const results = [];\n for (const block of data.content) {\n if (block.type === \"tool_use\") {\n const result = await runTool(block.name, block.input, residentFlat);\n results.push({ type: \"tool_result\", tool_use_id: block.id, content: JSON.stringify(result) });\n }\n }\n messages.push({ role: \"user\", content: results });\n continue;\n }\n if (data && Array.isArray(data.content)) { for (const b of data.content) { if (b && b.type === \"text\" && typeof b.text === \"string\") b.text = stripCites(b.text); } }\n return json(data, 200);\n }\n return json({ error: \"The assistant took too many steps. Please try again.\" }, 500);\n } catch (e) {\n return json({ error: \"Something went wrong reaching the assistant.\" }, 500);\n }\n }\n\n let _page;\n try { _page = await getPage(); }\n catch (e) { return new Response(\"AskAOAOA \\u2014 frontend not linked.\\n\\n\" + (e && e.message ? e.message : String(e)), { status: 500, headers: { \"content-type\": \"text/plain; charset=utf-8\" } }); }\n return new Response(_page, { headers: { \"content-type\": \"text/html; charset=utf-8\" } });\n}\n\nfunction json(obj, status) {\n return new Response(JSON.stringify(obj), { status: status || 200, headers: { \"content-type\": \"application/json\" } });\n}","// AskAOAOA — Val Town HTTP val. Env vars: ANTHROPIC_API_KEY, DATA_URL (knowledge val module URL), PAGE_URL (frontend val module URL\n// of your bye-law data val), ACCESS_CODE, SHEET_WEBHOOK_URL, SHEET_SECRET. Sheet link lives only in the Apps Script.\n\n// Bye-law knowledge lives in a separate val; set DATA_URL to its module URL.\nlet SYSTEM_CACHE = null;\nasync function getSystem() {\n if (SYSTEM_CACHE != null) return SYSTEM_CACHE;\n const u = Deno.env.get(\"DATA_URL\");\n if (!u) throw new Error(\"DATA_URL not set\");\n const mod = await import(u);\n SYSTEM_CACHE = mod.SYSTEM || \"\";\n return SYSTEM_CACHE;\n}\n\n// Web frontend lives in a separate val; set PAGE_URL to its module URL.\nlet PAGE_CACHE = null;\nasync function getPage() {\n if (PAGE_CACHE != null) return PAGE_CACHE;\n const u = Deno.env.get(\"PAGE_URL\");\n if (!u) {\n throw new Error(\n \"PAGE_URL is not set. Set it to the page val's MODULE url (esm.town/v/...) \\u2014 the same kind of url as DATA_URL, from the val's '\\u22ee \\u2192 Copy module URL' menu. It must NOT be the .val.run endpoint.\",\n );\n }\n if (/\\.val\\.run/i.test(u)) {\n throw new Error(\n \"PAGE_URL looks like a .val.run endpoint (\" + u +\n \"). Use the page val's MODULE url instead: open the page val, '\\u22ee \\u2192 Copy module URL' (esm.town/v/...).\",\n );\n }\n let mod;\n try {\n mod = await import(u);\n } catch (e) {\n throw new Error(\n \"Could not import PAGE_URL (\" + u +\n \"). Check it is the page val's module url and the val is saved. Details: \" +\n (e && e.message ? e.message : e),\n );\n }\n if (!mod || typeof mod.PAGE !== \"string\" || !mod.PAGE) {\n throw new Error(\n 'PAGE_URL imported, but it has no non-empty PAGE export. The page val must contain: export const PAGE = \"...\"; (re-save it and remove any ?v= from the url).',\n );\n }\n PAGE_CACHE = mod.PAGE;\n return PAGE_CACHE;\n}\n\nconst TOPICS = [\n \"Finance\",\n \"Admin & Communication\",\n \"Security/Parking\",\n \"MEP (Mechanical, Electrical, Plumbing)\",\n \"Gardening\",\n \"AMCs & FMS\",\n \"Housekeeping\",\n \"Tech/IT (including MyGate)\",\n \"Water Management\",\n \"Clubhouse Management\",\n \"Others\",\n];\n\nconst TOOLS = [\n {\n name: \"log_suggestion\",\n description:\n \"Save a resident's suggestion, feedback, or concern the MOMENT you have the topic and the text \\u2014 before asking anything else. Returns a reference number.\",\n input_schema: {\n type: \"object\",\n properties: {\n topic: {\n type: \"string\",\n enum: TOPICS,\n description: \"The single best-fitting topic.\",\n },\n suggestion: {\n type: \"string\",\n description: \"What the resident wants to say, in their own words.\",\n },\n },\n required: [\"topic\", \"suggestion\"],\n },\n },\n {\n name: \"update_suggestion\",\n description:\n \"Add the subcommittee answer, name, and/or email to a suggestion already saved with log_suggestion, using its reference. Call once per add-on as answered.\",\n input_schema: {\n type: \"object\",\n properties: {\n reference: {\n type: \"string\",\n description: \"The reference number returned by log_suggestion.\",\n },\n willing_to_join_subcommittee: {\n type: \"boolean\",\n description:\n \"The resident's Yes/No answer about helping on a subcommittee.\",\n },\n name: {\n type: \"string\",\n description: \"The resident's name, if shared.\",\n },\n email: {\n type: \"string\",\n description: \"The resident's email, if shared.\",\n },\n },\n required: [\"reference\"],\n },\n },\n {\n name: \"log_escalation\",\n description:\n \"Escalate an unresolved maintenance issue to the Managing Committee. Call ONLY after confirming an existing MyGate helpdesk ticket, with its ID and creation date in YYYY-MM-DD. Refused unless the ticket is more than a day old.\",\n input_schema: {\n type: \"object\",\n properties: {\n category: {\n type: \"string\",\n enum: TOPICS,\n description: \"The single best-fitting topic.\",\n },\n issue: {\n type: \"string\",\n description: \"Short description of the unresolved issue.\",\n },\n ticket_id: {\n type: \"string\",\n description: \"The MyGate helpdesk ticket ID / number.\",\n },\n ticket_created_date: {\n type: \"string\",\n description:\n \"Ticket creation date resolved to YYYY-MM-DD using today's date.\",\n },\n name: {\n type: \"string\",\n description:\n \"Optional: the resident's name for the committee's reference.\",\n },\n email: {\n type: \"string\",\n description:\n \"Optional: the resident's email, so the committee can copy them on it and follow up.\",\n },\n },\n required: [\"category\", \"issue\", \"ticket_id\", \"ticket_created_date\"],\n },\n },\n {\n name: \"log_question\",\n description:\n \"Send a resident's question to the Managing Committee. ONLY use this when the answer is genuinely NOT in the documents — always try to answer from the documents first. Email is required so the committee can reply.\",\n input_schema: {\n type: \"object\",\n properties: {\n topic: {\n type: \"string\",\n enum: TOPICS,\n description: \"The single best-fitting topic.\",\n },\n question: {\n type: \"string\",\n description: \"The resident's question, in their own words.\",\n },\n email: {\n type: \"string\",\n description:\n \"The resident's email — REQUIRED so the committee can reply.\",\n },\n name: { type: \"string\", description: \"Optional: the resident's name.\" },\n },\n required: [\"topic\", \"question\", \"email\"],\n },\n },\n {\n name: \"log_complaint\",\n description:\n \"Log a maintenance complaint directly, tracked by the assistant. Mints a reference (AO-C-...) and notifies the committee. Use for a problem the resident wants fixed (leak, broken light, lift, water, etc.).\",\n input_schema: {\n type: \"object\",\n properties: {\n category: {\n type: \"string\",\n enum: TOPICS,\n description: \"The single best-fitting area.\",\n },\n issue: {\n type: \"string\",\n description:\n \"Short description of the problem, in the resident's words.\",\n },\n name: { type: \"string\", description: \"Optional: the resident's name.\" },\n email: {\n type: \"string\",\n description:\n \"REQUIRED: the resident's email, so the committee can follow up and copy them in on the complaint.\",\n },\n },\n required: [\"category\", \"issue\", \"email\"],\n },\n },\n {\n name: \"update_complaint\",\n description:\n \"Add or correct the resident's name and/or email on a complaint ALREADY saved with log_complaint, using its reference. ALWAYS use this for name/email that arrive after logging \\u2014 never call log_complaint again (that creates a duplicate). Providing an email notifies the committee with the resident in copy.\",\n input_schema: {\n type: \"object\",\n properties: {\n reference: {\n type: \"string\",\n description: \"The AO-C-... reference returned by log_complaint.\",\n },\n name: {\n type: \"string\",\n description: \"The resident's name (optional).\",\n },\n email: {\n type: \"string\",\n description: \"The resident's email (optional).\",\n },\n },\n required: [\"reference\"],\n },\n },\n {\n name: \"check_complaint_status\",\n description:\n \"Look up the status the committee has set for the resident's maintenance complaint(s). Pass a reference if the resident gave one (like AO-C-...); otherwise it returns recent complaints for their flat.\",\n input_schema: {\n type: \"object\",\n properties: {\n reference: {\n type: \"string\",\n description: \"Optional: a complaint reference the resident provided.\",\n },\n },\n required: [],\n },\n },\n {\n name: \"get_resident_info\",\n description:\n \"Look up the committee's record for THIS resident's own flat (e.g. pending maintenance dues, registered owner name, notes). Uses their flat automatically and only ever returns their own flat's record. Use it when the resident asks about their own account or dues.\",\n input_schema: { type: \"object\", properties: {}, required: [] },\n },\n {\n name: \"log_recommendation\",\n description:\n \"Save a neighbour's recommendation of anything nearby — a service, shop, place, or vendor (dentist, hospital, hotel, restaurant, hardware shop, plumber, electrician, tutor, cook, etc.) so other residents can benefit. Call once you have at least what kind of thing it is and its name.\",\n input_schema: {\n type: \"object\",\n properties: {\n category: {\n type: \"string\",\n description:\n \"What kind of thing it is, e.g. Dentist, Hospital, Restaurant, Hotel, Hardware shop, Plumber, Tutor.\",\n },\n provider: {\n type: \"string\",\n description: \"Name of the person or business being recommended.\",\n },\n contact: {\n type: \"string\",\n description: \"Phone number or contact detail, if shared.\",\n },\n area: { type: \"string\", description: \"Area or locality, if shared.\" },\n note: {\n type: \"string\",\n description: \"Short note on why it's recommended, if shared.\",\n },\n credit: {\n type: \"boolean\",\n description:\n \"Whether the resident agreed to have their flat shown as the recommender. Set false if they preferred to stay anonymous or you're unsure.\",\n },\n },\n required: [\"category\", \"provider\"],\n },\n },\n {\n name: \"get_recommendations\",\n description:\n \"Find neighbour recommendations for a kind of service the resident is asking about (e.g. 'dentist', 'pediatrician', 'bird netting'). Returns providers other residents have recommended, with who recommended each.\",\n input_schema: {\n type: \"object\",\n properties: {\n query: {\n type: \"string\",\n description:\n \"Short search term for what they want, e.g. 'dentist', 'hardware shop', 'restaurant', 'hotel'.\",\n },\n },\n required: [\"query\"],\n },\n },\n {\n name: \"get_mc_contacts\",\n description:\n \"Get the committee directory: office-bearer POSTS (President, Secretary, Treasurer, etc.) and work PORTFOLIOS (Finance, Water, etc.), each tagged with a Type, plus the members / points of contact, official emails, and phone numbers. Use when a resident asks who holds a post, who to contact for an area, or how to email the committee.\",\n input_schema: { type: \"object\", properties: {}, required: [] },\n },\n];\n\nconst FMS_CONTACT = \"Sandeep on +91 91108 02505\";\n\nconst ACTIONS = `\n\nYou can also help with the actions below using your tools. Ask one thing at a time; act only on the resident's clear go-ahead. Never invent a reference number \\u2014 use only the one a tool returns.\nPickers: end a message with [[PICK_TOPIC]] (areas dropdown), [[PICK_YESNO]] (Yes/No), or [[PICK_DATE]] (calendar). When you show a picker, do not also ask them to type.\n\n1) SUGGESTIONS, FEEDBACK & CONCERNS (log_suggestion, then update_suggestion)\nFor any idea, feedback, complaint or concern that is NOT a live maintenance work-order (e.g. a security lapse, a bill not delivered, an idea like EV charging):\n- Ask which area it fits, ending with [[PICK_TOPIC]].\n- Capture what they want to say in their words.\n- As soon as you have the area and the text, call log_suggestion ONCE to save it; tell them it's recorded and give the reference number. Remember that reference. Do NOT call log_suggestion again for this item — for every detail below, use update_suggestion with that SAME reference.\n- Add-ons (all optional), using update_suggestion(reference, ...):\n - For an improvement idea (not a pure complaint), warmly ask (ending with [[PICK_YESNO]]) if they'd help on a subcommittee, then update_suggestion(reference, willing_to_join_subcommittee). Skip this for a complaint or concern.\n - Then, in ONE message, ask whether they'd like to add their name and/or an email for updates — make clear both are optional. When they reply, call update_suggestion ONCE with whatever they shared (reference, name and/or email). If they skip either or both, that's fine — the flat already identifies them. Do not ask for name and email in two separate turns.\n- For a safety concern (e.g. a security lapse), also gently advise them to tell Security or the MC directly, right away.\n\n2) MAINTENANCE COMPLAINTS (log_complaint, then update_complaint / check_complaint_status)\nWhen a resident reports a maintenance problem they want fixed (a leak, a broken light, a lift or water issue, etc.):\n- If YOU offer to log a complaint (rather than the resident directly asking you to), end that offer with [[PICK_YESNO]] so they get tappable Yes/No buttons.\n- Capture a short, clear description of the problem, and ask which area it fits, ending with [[PICK_TOPIC]].\n- Ask for their email address — this is REQUIRED so the committee can follow up and copy them in — and, in the SAME message, optionally their name. If they don't give an email, briefly explain the committee needs it to follow up on the complaint, and ask once more; do NOT log the complaint until you have an email.\n- Then call log_complaint(category, issue, email, name?) ONCE. Give them the reference it returns (it looks like AO-C-...); the committee is emailed with the resident in copy. Do NOT call log_complaint again for this item — if they later want to correct a detail, use update_complaint(reference, ...).\nChecking status: when a resident asks about their complaint(s), or gives a reference like AO-C-..., call check_complaint_status (pass the reference if they gave one; otherwise it returns recent complaints for their flat). Tell them the current status the committee has set (e.g. Open, In Progress, Resolved). If nothing is found, say so kindly and offer to log a new complaint.\n\n3) ESCALATING AN EXISTING MYGATE TICKET (log_escalation)\nUse this only when the resident has ALREADY raised a ticket on the MyGate helpdesk that has stayed unresolved. To report a fresh problem, use pathway 2 (complaints) instead.\n- Confirm they already have a MyGate ticket, ending with [[PICK_YESNO]].\n- If NO: they don't need a MyGate ticket to report a problem — offer to log it directly as a complaint here (pathway 2). Log nothing under escalation.\n- If YES: get the ticket ID and a short description. Ask its category ([[PICK_TOPIC]]) and its creation date ([[PICK_DATE]]).\n- Resolve the date to YYYY-MM-DD using TODAY'S DATE (below); assume the current year; read it back to confirm.\n- Before logging, ask in ONE message whether they'd like to add their name and email so the committee can keep them posted and copy them on it — both optional; pass whatever they share.\n- Call log_escalation. It logs ONLY if the ticket is over a day old; if the tool says it's still within a day, do NOT retry \\u2014 kindly ask them to wait a little longer so the facility team (FMS) can act.\n- On a successful escalation, confirm with the reference, and also remind the resident that they can follow up on it directly by calling the FMS (facility) manager, ${FMS_CONTACT}. Then offer to attach a photo of the issue by ending that message with [[ATTACH:REF]] where REF is that reference number (an upload button appears). Screenshots are for escalated issues only.\n\n4) QUESTIONS FOR THE MANAGING COMMITTEE (log_question)\nWhen a resident asks a question, ALWAYS try to answer it from the documents first. If you can answer, just answer and cite the clause/section — log nothing.\n- Only if the answer is genuinely NOT in the documents (you would otherwise say it's Not covered): tell the resident you'll pass it to the Managing Committee, and offer to send it for them.\n- If they agree, ask which area it fits, ending with [[PICK_TOPIC]]. Then, in ONE message, ask for their name and email — the EMAIL IS REQUIRED so the committee can reply; the name is optional. If they won't share an email, explain you can't forward it without a way to reach them (they're welcome to raise it another way).\n- Once you have the question, the area, and an email, call log_question(topic, question, email, name). Confirm it has been sent to the committee and give the reference number.\n\n5) PERSONAL ACCOUNT (get_resident_info)\nWhen a resident asks about their own account \\u2014 pending maintenance dues, their registered owner name, or other details the committee keeps for their flat \\u2014 call get_resident_info (it uses their flat automatically) and answer from the record it returns. If no record is found, or a field is blank, say you don't have that on record and suggest they check with the association office. Only ever discuss their own flat's details.\n\n6) NEIGHBOUR RECOMMENDATIONS (log_recommendation, get_recommendations)\nResidents trust each other's recommendations for anything nearby — dentists, doctors and hospitals, restaurants and hotels, hardware and grocery shops, plumbers, electricians, tutors, cooks, vendors, and so on. Help capture and share these.\n- If a resident shares a recommendation, capture the type of service, the provider's name, and any contact, area, or note they give. Then ask, ending with [[PICK_YESNO]], whether you may credit their flat when neighbours ask (Yes) or keep it anonymous (No). Call log_recommendation with what you have and set credit from their answer. Thank them warmly.\n- When a resident asks for a recommendation (e.g. \"any good dentists nearby?\", \"who do people use for bird netting?\"), call get_recommendations with a short query, then suggest one or two names with their contact/area if known, and say WHO recommended them (e.g. \"recommended by 602-C and 1103-B\") — this neighbour trust is the whole point. If a recommender chose to stay anonymous, say \"recommended by a resident\". If several residents recommended the same name, mention that. If nothing matches, say so kindly and invite them to share one if they know a good option.\n- Residents may forward or paste a recommendation they saw in the community WhatsApp group — accept these, pull out the details, and log them. If one message contains several recommendations, log each one, then briefly confirm what you saved.\n- Whenever you help with a recommendation — or have none to offer — warmly invite the resident to share any good contacts they know, so the shared directory grows for everyone.\n\n7) MC POSTS, PORTFOLIOS & CONTACTS (get_mc_contacts)\nThe committee directory is one sheet with two kinds of entries, each row marked with a Type of \"Post\" or \"Portfolio\":\n- POSTS are the office-bearers held by members (e.g. President, Joint President, Secretary, Joint Secretary, Treasurer, Joint Treasurer, Managing Committee, Association Members).\n- PORTFOLIOS are areas of work that mirror the topic list (e.g. Finance, Security/Parking, Water Management, Housekeeping).\nEach entry has a name, the member / point-of-contact, a phone, and sometimes an official email. Always call get_mc_contacts and answer ONLY from what it returns:\n- \"Who are the office-bearers / what posts do members hold / who is the President, Secretary, etc.\" -> list the POSTS (type = Post) with the member's name and phone number.\n- \"What portfolios does the committee have / who handles water, security, etc.\" -> list or match the PORTFOLIOS (type = Portfolio) with their point of contact.\n- \"What email do I write to / how do I email the committee\" -> share ONLY the email addresses get_mc_contacts actually returns (these are already limited to the official association addresses). Never turn a phone number into an email or invent an address; if none is returned for what they need, point them to the general Managing Committee entry or the association office.\n- Some rows may have a blank Type (for example a general \"Managing Committee\" contact whose email residents write to). Treat a blank-Type row as a contact/email entry only: use its official email when asked how to reach the committee, but do NOT list it among the posts or the portfolios.\n- Never invent a name, post, portfolio, email, or number -- share only what get_mc_contacts returns.\n\nAnswer ordinary questions from the documents as usual; only log a question when you genuinely cannot answer it.`;\n\nconst WEBHOOK = Deno.env.get(\"SHEET_WEBHOOK_URL\") || \"\";\nconst SHEET_SECRET = Deno.env.get(\"SHEET_SECRET\") || \"\";\nconst MC_CODE = Deno.env.get(\"MC_ACCESS_CODE\") || \"\";\nfunction mcAccepts(c) {\n return !!MC_CODE && String(c || \"\").trim() === MC_CODE;\n}\n\nconst RAW_ACCESS = (Deno.env.get(\"ACCESS_CODE\") || \"\").trim();\nlet MODE = \"off\", SHARED = \"\";\nif (RAW_ACCESS.length) {\n if (RAW_ACCESS.toLowerCase() === \"flat\") MODE = \"flat\";\n else {\n MODE = \"code\";\n SHARED = RAW_ACCESS;\n }\n}\nconst gateOn = MODE !== \"off\";\n\nfunction isValidFlat(raw) {\n const s = String(raw || \"\").trim().toLowerCase().replace(/\\s+/g, \"\");\n const m = s.match(/^(\\d{3,4})-?([a-d])$/) || s.match(/^([a-d])-?(\\d{3,4})$/);\n if (!m) return false;\n let digits, block;\n if (/^\\d/.test(m[1])) {\n digits = m[1];\n block = m[2];\n } else {\n block = m[1];\n digits = m[2];\n }\n const flat = parseInt(digits.slice(-2), 10);\n const series = parseInt(digits.slice(0, -2), 10);\n const maxSeries = (block === \"a\" || block === \"b\") ? 11 : 10;\n const maxFlat = (block === \"a\") ? 6 : 4;\n if (!(series >= 1 && series <= maxSeries)) return false;\n if (!(flat >= 1 && flat <= maxFlat)) return false;\n return true;\n}\nfunction accepts(code) {\n if (MODE === \"off\") return true;\n if (MODE === \"flat\") return isValidFlat(code);\n return String(code || \"\").trim().toLowerCase() === SHARED.toLowerCase();\n}\n\nfunction istNow() {\n return new Date(Date.now() + 5.5 * 3600 * 1000);\n}\nfunction istTodayISO() {\n const d = istNow();\n return d.getUTCFullYear() + \"-\" +\n String(d.getUTCMonth() + 1).padStart(2, \"0\") + \"-\" +\n String(d.getUTCDate()).padStart(2, \"0\");\n}\nfunction daysSince(dateStr) {\n const m = String(dateStr || \"\").match(/^(\\d{4})-(\\d{2})-(\\d{2})$/);\n if (!m) return null;\n const created = Date.UTC(+m[1], +m[2] - 1, +m[3]);\n if (isNaN(created)) return null;\n const d = istNow();\n const today = Date.UTC(d.getUTCFullYear(), d.getUTCMonth(), d.getUTCDate());\n return Math.floor((today - created) / 86400000);\n}\n\nasync function postSheet(payload) {\n if (!WEBHOOK) {\n return {\n ok: false,\n note: \"Logging is not set up yet (no SHEET_WEBHOOK_URL).\",\n };\n }\n try {\n if (SHEET_SECRET) payload.secret = SHEET_SECRET;\n const r = await fetch(WEBHOOK, {\n method: \"POST\",\n headers: { \"content-type\": \"application/json\" },\n body: JSON.stringify(payload),\n });\n const d = await r.json();\n return (d && d.ok)\n ? { ok: true, reference: d.reference, url: d.url }\n : { ok: false, note: \"The logging service reported an error.\" };\n } catch (e) {\n return { ok: false, note: \"Could not reach the logging service.\" };\n }\n}\n\nlet STATUS_CACHE = { t: 0, v: \"\" };\nasync function sheetGet(query) {\n if (!WEBHOOK) {\n return {\n ok: false,\n note: \"Lookups are not set up yet (no SHEET_WEBHOOK_URL).\",\n };\n }\n try {\n const url = WEBHOOK + \"?\" + query +\n (SHEET_SECRET ? \"&secret=\" + encodeURIComponent(SHEET_SECRET) : \"\");\n const r = await fetch(url, { redirect: \"follow\" });\n return await r.json();\n } catch (e) {\n return { ok: false, note: \"Could not reach the lookup service.\" };\n }\n}\nasync function getStatus() {\n const now = Date.now();\n if (now - STATUS_CACHE.t < 60000) return STATUS_CACHE.v;\n let v = \"\";\n try {\n const d = await sheetGet(\"q=status\");\n if (d && d.ok && Array.isArray(d.active) && d.active.length) {\n v = d.active.map((a) => (a && a.message != null) ? a.message : a).filter(\n Boolean,\n ).join(\" | \");\n }\n } catch (e) {}\n STATUS_CACHE = { t: now, v: v };\n return v;\n}\n\nconst SYSTEM_COPILOT =\n \"You are the AskAOAOA Committee Copilot for the Managing Committee (MC) of Aryan Opulence Apartments, a 189-flat community. You are given recent community data as JSON (complaints with status, suggestions, questions, escalations, site-status posts), newest first. Help the committee: summarise and count, spot recurring themes, list open/pending items and prioritise them, and draft clear courteous communications (notices, replies to residents, AGM agenda items). Base everything strictly on the data provided; never invent numbers, references, names, or records; if it is not in the data, say so plainly. Complaint status is in the 'Status' field (Open / In Progress / Resolved); complaints look like AO-C-... Cite references and flats where it helps the committee act. Dates are IST; interpret 'this week' / 'this month' relative to the date given. Be concise and action-oriented; use short bullet lists for summaries and a warm, professional tone for drafts. This data is confidential to the committee. You are advisory \\u2014 you do not send messages or change any records. You also have the association's official documents as reference; when the committee asks a rules question, you MAY answer with the exact clause or section numbers (this is committee-only \\u2014 residents never receive clause numbers).\";\n\nasync function copilotAnswer(KEY, history, sys) {\n const dd = await sheetGet(\"q=export\");\n const dataStr = (dd && dd.ok && dd.data)\n ? JSON.stringify(dd.data)\n : \"(no data available)\";\n const system = [\n {\n type: \"text\",\n text: SYSTEM_COPILOT,\n cache_control: { type: \"ephemeral\" },\n },\n ];\n if (sys) {\n system.push({\n type: \"text\",\n text:\n \"REFERENCE \\u2014 the association's official documents. For the committee you MAY quote exact clause and section numbers here (residents never see these):\\n\\n\" +\n sys,\n cache_control: { type: \"ephemeral\" },\n });\n }\n system.push({\n type: \"text\",\n text: \"Today's date: \" + istTodayISO() +\n \" (IST).\\n\\nCOMMUNITY DATA (JSON, newest first):\\n\" + dataStr,\n });\n const msgs = history.slice(-12).map((m) => ({\n role: m && m.role === \"assistant\" ? \"assistant\" : \"user\",\n content: String((m && m.content) || \"\").slice(0, 6000),\n }));\n try {\n const r = await fetch(\"https://api.anthropic.com/v1/messages\", {\n method: \"POST\",\n headers: {\n \"content-type\": \"application/json\",\n \"x-api-key\": KEY,\n \"anthropic-version\": \"2023-06-01\",\n },\n body: JSON.stringify({\n model: \"claude-sonnet-4-6\",\n max_tokens: 2000,\n system: system,\n messages: msgs,\n }),\n });\n const cd = await r.json();\n if (r.status !== 200) {\n return \"The copilot is having trouble right now. Please try again.\";\n }\n return (cd.content || []).map((c) => c.type === \"text\" ? c.text : \"\")\n .filter(Boolean).join(\"\\n\").trim() ||\n \"I couldn't produce an answer for that.\";\n } catch (e) {\n return \"The copilot couldn't reach the service just now.\";\n }\n}\n\nfunction complaintRef(t) {\n const m = String(t || \"\").match(/AO-C-\\d{6}-\\d{4}/i);\n return m ? m[0].toUpperCase() : \"\";\n}\nfunction isComplaintStatus(t) {\n const s = String(t || \"\").trim().toLowerCase().replace(/[?.!]+$/, \"\");\n if (complaintRef(s)) return true;\n return [\n \"my complaints\",\n \"my complaint\",\n \"complaint status\",\n \"complaints status\",\n \"check my complaints\",\n \"check my complaint\",\n \"check complaint status\",\n \"status of my complaint\",\n \"status of my complaints\",\n \"track my complaint\",\n \"track my complaints\",\n \"complaint update\",\n \"complaint updates\",\n ].includes(s);\n}\nfunction formatComplaintsWeb(d, ref) {\n if (!d || !d.ok) {\n return \"I couldn't check the complaint status just now. Please try again in a moment.\";\n }\n const list = d.complaints || [];\n if (!list.length) {\n return ref\n ? \"I couldn't find a complaint with that reference. Please double-check it (it looks like AO-C-...), or describe the issue and I'll log a new complaint.\"\n : \"You don't have any complaints logged yet. If something needs fixing, just describe it and I'll raise a complaint for you.\";\n }\n const lines = list.map(function (c) {\n return \"\\u2022 \" + (c.reference || \"\") + \" \\u2014 \" + (c.category || \"\") +\n \": \" + (c.issue || \"\") + \" [Status: \" + (c.status || \"Open\") + \"]\";\n });\n return \"Here's the latest on your complaint\" + (list.length > 1 ? \"s\" : \"\") +\n \":\\n\\n\" + lines.join(\"\\n\");\n}\n\n// Remove bye-law/clause/section NUMBERS from resident-facing replies (keep the plain answer).\nfunction stripCites(t) {\n if (!t) return t;\n let s = String(t);\n // parenthetical citations that contain a clause/section number, e.g. *(Bye-Laws, Clause 3.12)*\n s = s.replace(\n /\\*?\\s*\$(?:[^()]*?)(?:clause|section|article|rule|bye-?law|point|item|para(?:graph)?)\\s*\\d+[a-z]?(?:\\.\\d+)*(?:[^()]*?)\$\\s*\\*?/gi,\n \"\",\n );\n // inline references, e.g. \"Clause 43.9\", \"Section 14\", \"Bye-Law 11.3\"\n s = s.replace(\n /\\b(?:bye-?laws?[,\\s]*)?(?:clause|section|article|bye-?law)s?\\s*\\d+[a-z]?(?:\\.\\d+)*(?:\\s*(?:,|and|&)\\s*\\d+[a-z]?(?:\\.\\d+)*)*/gi,\n \"the association's rules\",\n );\n // tidy residue\n s = s.replace(/\$\\s*\$/g, \"\");\n s = s.replace(/[ \\t]{2,}/g, \" \");\n s = s.replace(/\\s+([.,;:])/g, \"$1\");\n s = s.replace(\n /the association's rules(?:\\s*(?:,|and|&)\\s*the association's rules)+/gi,\n \"the association's rules\",\n );\n return s.trim();\n}\n\nasync function runTool(name, input, flat) {\n input = input || {};\n if (name === \"log_suggestion\") {\n return await postSheet({\n type: \"suggestion\",\n topic: input.topic || \"\",\n suggestion: input.suggestion || \"\",\n flat: flat || \"\",\n });\n }\n if (name === \"update_suggestion\") {\n const payload = {\n type: \"suggestion_update\",\n reference: input.reference || \"\",\n };\n if (typeof input.willing_to_join_subcommittee === \"boolean\") {\n payload.joinSubcommittee = input.willing_to_join_subcommittee;\n }\n if (input.name) payload.name = input.name;\n if (input.email) payload.email = input.email;\n return await postSheet(payload);\n }\n if (name === \"log_escalation\") {\n const days = daysSince(input.ticket_created_date);\n if (days === null) {\n return {\n ok: false,\n note:\n \"The ticket date was not understood. Ask the resident to pick it with the date picker (YYYY-MM-DD).\",\n };\n }\n if (days < 0) {\n return {\n ok: false,\n note:\n \"That ticket date is in the future. Ask the resident to re-check and pick the correct date.\",\n };\n }\n if (days < 1) {\n return {\n ok: false,\n note:\n \"The MyGate ticket was created today, less than a day ago. Do NOT escalate yet. Kindly ask the resident to wait a little longer so the facility team (FMS) can act, and to escalate once it is more than a day old. If they'd like to nudge it sooner, they can call the FMS manager, \" +\n FMS_CONTACT + \".\",\n };\n }\n return await postSheet({\n type: \"escalation\",\n name: input.name || \"\",\n flat: flat || \"\",\n category: input.category || \"\",\n issue: input.issue || \"\",\n ticketNo: input.ticket_id || \"\",\n ticketDate: input.ticket_created_date || \"\",\n daysOpen: days,\n email: input.email || \"\",\n });\n }\n if (name === \"log_question\") {\n if (!input.email) {\n return {\n ok: false,\n note:\n \"An email is required so the committee can reply. Please ask the resident for an email before logging the question.\",\n };\n }\n return await postSheet({\n type: \"question\",\n topic: input.topic || \"\",\n question: input.question || \"\",\n email: input.email || \"\",\n name: input.name || \"\",\n flat: flat || \"\",\n });\n }\n if (name === \"log_complaint\") {\n if (!input.email) {\n return {\n ok: false,\n note:\n \"An email is required so the committee can follow up and copy the resident in. Please ask the resident for an email before logging the complaint.\",\n };\n }\n return await postSheet({\n type: \"complaint\",\n category: input.category || \"\",\n issue: input.issue || \"\",\n name: input.name || \"\",\n email: input.email || \"\",\n flat: flat || \"\",\n });\n }\n if (name === \"update_complaint\") {\n return await postSheet({\n type: \"complaint_update\",\n reference: input.reference || \"\",\n name: input.name || \"\",\n email: input.email || \"\",\n });\n }\n if (name === \"check_complaint_status\") {\n let query = \"q=complaint&flat=\" + encodeURIComponent(flat || \"\");\n if (input.reference) {\n query += \"&ref=\" + encodeURIComponent(String(input.reference).trim());\n }\n return await sheetGet(query);\n }\n if (name === \"get_resident_info\") {\n if (!flat) {\n return {\n ok: false,\n note: \"The resident's flat isn't known yet; ask for their flat first.\",\n };\n }\n return await sheetGet(\"q=resident&flat=\" + encodeURIComponent(flat));\n }\n if (name === \"log_recommendation\") {\n return await postSheet({\n type: \"recommendation\",\n category: input.category || \"\",\n provider: input.provider || \"\",\n contact: input.contact || \"\",\n area: input.area || \"\",\n note: input.note || \"\",\n credit: !!input.credit,\n flat: flat || \"\",\n });\n }\n if (name === \"get_recommendations\") {\n return await sheetGet(\n \"q=recommend&query=\" + encodeURIComponent(input.query || \"\"),\n );\n }\n if (name === \"get_mc_contacts\") {\n return await sheetGet(\"q=mc\");\n }\n return { ok: false, note: \"Unknown action.\" };\n}\n\nasync function callClaude(KEY, systemBlocks, messages) {\n const r = await fetch(\"https://api.anthropic.com/v1/messages\", {\n method: \"POST\",\n headers: {\n \"content-type\": \"application/json\",\n \"x-api-key\": KEY,\n \"anthropic-version\": \"2023-06-01\",\n },\n body: JSON.stringify({\n model: \"claude-sonnet-4-6\",\n max_tokens: 1000,\n system: systemBlocks,\n tools: TOOLS,\n messages,\n }),\n });\n return { status: r.status, data: await r.json() };\n}\n\nexport default async function (req) {\n const url = new URL(req.url);\n const KEY = Deno.env.get(\"ANTHROPIC_API_KEY\");\n\n if (url.pathname === \"/auth\") {\n if (req.method === \"GET\") {\n return json({\n required: gateOn,\n mode: MODE,\n label: MODE === \"flat\"\n ? \"Enter your flat number to continue.\"\n : \"Enter the resident access code to continue.\",\n placeholder: MODE === \"flat\" ? \"flat-block\" : \"Access code\",\n });\n }\n if (req.method === \"POST\") {\n let code = \"\";\n try {\n const b = await req.json();\n code = String((b && b.code) || \"\");\n } catch (e) {}\n return json({ ok: accepts(code) });\n }\n }\n\n if (req.method === \"POST\" && url.pathname === \"/upload\") {\n let b;\n try {\n b = await req.json();\n } catch (e) {\n return json({ error: \"Bad request.\" }, 400);\n }\n if (gateOn && !accepts(b && b.code)) {\n return json({ error: \"unauthorized\" }, 401);\n }\n if (!b || !b.reference || !b.data) {\n return json({ ok: false, note: \"Missing screenshot data.\" }, 400);\n }\n const res = await postSheet({\n type: \"attachment\",\n reference: b.reference,\n data: b.data,\n mime: b.mime || \"image/png\",\n filename: b.filename || \"screenshot.png\",\n });\n return json(res, res.ok ? 200 : 500);\n }\n\n if (req.method === \"POST\" && url.pathname === \"/api\") {\n if (!KEY) {\n return json({\n error:\n \"The ANTHROPIC_API_KEY environment variable is not set on this val.\",\n }, 500);\n }\n\n let body;\n try {\n body = await req.json();\n } catch (e) {\n return json({ error: \"Bad request.\" }, 400);\n }\n\n // Committee copilot (MC-only, code-gated) — returns a Claude-shaped reply the page already renders.\n if (body && body.mode === \"copilot\") {\n if (!mcAccepts(body.mccode)) return json({ error: \"unauthorized\" }, 401);\n const inc = Array.isArray(body.messages) ? body.messages : [];\n if (!inc.length) return json({ error: \"No message provided.\" }, 400);\n let _sys = null;\n try {\n _sys = await getSystem();\n } catch (e) {}\n const reply = await copilotAnswer(KEY, inc, _sys);\n return json({\n content: [{ type: \"text\", text: reply }],\n stop_reason: \"end_turn\",\n }, 200);\n }\n\n let SYSTEM;\n try {\n SYSTEM = await getSystem();\n } catch (e) {\n return json({\n error:\n \"Bye-law data not linked yet. Set the DATA_URL environment variable to your data val's module URL.\",\n }, 500);\n }\n\n if (gateOn && !accepts(body && body.code)) {\n return json({ error: \"Access code required or incorrect.\" }, 401);\n }\n\n const residentFlat = (MODE === \"flat\")\n ? String((body && body.code) || \"\").trim().toUpperCase()\n : \"\";\n const incoming = Array.isArray(body.messages) ? body.messages : [];\n if (!incoming.length) return json({ error: \"No message provided.\" }, 400);\n\n // Deterministic (no-LLM) complaint-status lookup for clear status intents\n {\n const lastUser = incoming[incoming.length - 1];\n const lastText = (lastUser && lastUser.role !== \"assistant\")\n ? String(lastUser.content || \"\")\n : \"\";\n const cref = complaintRef(lastText);\n if (isComplaintStatus(lastText) && (residentFlat || cref)) {\n let cq = \"q=complaint&flat=\" + encodeURIComponent(residentFlat || \"\");\n if (cref) cq += \"&ref=\" + encodeURIComponent(cref);\n const cd = await sheetGet(cq);\n return json({\n content: [{ type: \"text\", text: formatComplaintsWeb(cd, cref) }],\n }, 200);\n }\n }\n\n const lang = (body && body.lang) || \"en\";\n const langLine = lang === \"hi\"\n ? \" Reply to the resident in Hindi (Devanagari script). Keep any line that starts with 'VERDICT:' and its label in English exactly, and keep any [[...]] tokens exactly as written.\"\n : lang === \"kn\"\n ? \" Reply to the resident in Kannada. Keep any line that starts with 'VERDICT:' and its label in English exactly, and keep any [[...]] tokens exactly as written.\"\n : \"\";\n\n let messages = incoming.slice(-14).map((m) => ({\n role: m && m.role === \"assistant\" ? \"assistant\" : \"user\",\n content: String((m && m.content) || \"\").slice(0, 4000),\n }));\n\n const priorRefs = [];\n for (const m of messages) {\n if (m.role !== \"assistant\") continue;\n const found = m.content.match(/AO-(?:C-)?\\d{6}-\\d{4}/g);\n if (found) {\n for (const r of found) if (!priorRefs.includes(r)) priorRefs.push(r);\n }\n }\n const refLine = priorRefs.length\n ? \" NOTE: This conversation has already saved record(s) with reference \" +\n priorRefs.join(\", \") +\n \". These are already logged. Do NOT call any log_ tool again for an item that already has a reference — that creates a duplicate. To add a name, email, or other detail, use the matching UPDATE tool: update_suggestion for a suggestion reference, or update_complaint for an AO-C-... complaint reference. Only log a brand-new, clearly different item the resident raises now.\"\n : \"\";\n\n const siteStatus = await getStatus();\n const statusLine = siteStatus\n ? \" CURRENT SITE STATUS (live alerts posted by the committee/security): \" +\n siteStatus +\n \". If the resident asks about power, water, lifts, or what's happening on site, tell them this.\"\n : \" CURRENT SITE STATUS: No site alerts are posted right now. If a resident reports a problem, do not claim everything is working \\u2014 suggest they contact security/FMS or log a complaint.\";\n\n const systemBlocks = [\n {\n type: \"text\",\n text: SYSTEM + ACTIONS,\n cache_control: { type: \"ephemeral\" },\n },\n {\n type: \"text\",\n text: \"Today's date is \" + istTodayISO() +\n \" (YYYY-MM-DD), India Standard Time. \" +\n (residentFlat\n ? \"The resident's flat is \" + residentFlat + \".\"\n : \"You do not yet know the resident's flat; if you need it for an action, ask for their flat number and block (A, B, C or D).\") +\n langLine + refLine + statusLine,\n },\n ];\n\n try {\n for (let step = 0; step < 6; step++) {\n const { status, data } = await callClaude(KEY, systemBlocks, messages);\n if (status !== 200) return json(data, status);\n if (data.stop_reason === \"tool_use\") {\n messages.push({ role: \"assistant\", content: data.content });\n const results = [];\n for (const block of data.content) {\n if (block.type === \"tool_use\") {\n const result = await runTool(\n block.name,\n block.input,\n residentFlat,\n );\n results.push({\n type: \"tool_result\",\n tool_use_id: block.id,\n content: JSON.stringify(result),\n });\n }\n }\n messages.push({ role: \"user\", content: results });\n continue;\n }\n if (data && Array.isArray(data.content)) {\n for (const b of data.content) {\n if (b && b.type === \"text\" && typeof b.text === \"string\") {\n b.text = stripCites(b.text);\n }\n }\n }\n return json(data, 200);\n }\n return json({\n error: \"The assistant took too many steps. Please try again.\",\n }, 500);\n } catch (e) {\n return json(\n { error: \"Something went wrong reaching the assistant.\" },\n 500,\n );\n }\n }\n\n let _page;\n try {\n _page = await getPage();\n } catch (e) {\n return new Response(\n \"AskAOAOA \\u2014 frontend not linked.\\n\\n\" +\n (e && e.message ? e.message : String(e)),\n { status: 500, headers: { \"content-type\": \"text/plain; charset=utf-8\" } },\n );\n }\n return new Response(_page, {\n headers: { \"content-type\": \"text/html; charset=utf-8\" },\n });\n}\n\nfunction json(obj, status) {\n return new Response(JSON.stringify(obj), {\n status: status || 200,\n headers: { \"content-type\": \"application/json\" },\n });\n}","createdAt",["D",1784872764062],"branchVersion","branchId","624491c7-35e4-41e1-bcdd-f028e6d18f83","id","7c9f1d75-2ce0-4053-b1a5-371b96e9689a","AskAOAOA",["D",1783155855780],"deletedAt","legacyEnvVars","privacy","public","httpPrivacy","description","AOAOA Chat Assistant","imageUrl","4a18de72-744a-4935-a405-7e9166d2bb8e","pinnedFileId","pinPreview","pinMigrated","screenshotVersion","likeCount",0,"orgId","019f2c5b-c205-7209-90ec-fea27dba2152","tursoName","7c9f1d752ce04053b1a5371b96e9689a","tursoHostname","7c9f1d752ce04053b1a5371b96e9689a-val-town.aws-us-east-2.turso.io","tursoMeasuredAt",["D",1789517443998],"pinned","userPerm","r","valPerm","blobPerm","rw","emailPerm","sqlitePerm","projectPerm","telemetryPerm","user",{"_98":97,"_106":102},"org",{"_98":97,"_99":100,"_101":102,"_18":55,"_103":104,"_105":25},"branch",{"_13":87,"_32":88,"_43":42,"_89":44,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":45,"_96":97},"isOwned",107,"main","projectId","forkedBranchId","forkedBranchVersion","forkedProjectPrivacy","forkedProjectId","forkedProjectOrgId","projectName","userHandle","sanair1992","handle","displayName","Shyam A Nair","avatar","https://lh3.googleusercontent.com/a/ACg8ocL6k5_PJu7Okt0TDOcmJDDE1rjDZi65QoH9WtDAlAU6jJixUNUydg=s96-c","tier","free","canRestrictVals","profileImageUrl","branchName","","adoptOrgId",{"_43":44,"_32":45,"_38":183,"_47":-5,"_48":25,"_49":50,"_51":50,"_52":53,"_54":-5,"_18":55,"_56":-5,"_57":25,"_58":-5,"_59":-5,"_60":61,"_62":63,"_64":65,"_66":67,"_68":184,"_70":-5,"_71":72,"_73":72,"_74":75,"_76":75,"_77":75,"_78":72,"_79":72,"_80":185,"_82":186,"_84":187,"_86":25},"tree",[170,171,172],"files",[170,171,172],"counts",{"_158":61,"_159":160,"_161":61,"_162":163,"_164":165},"contents",[130,131,132],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles",true,"grants","orgs","customDomains",{},{"_43":153,"_32":28,"_30":31,"_136":-5,"_41":42,"_40":14,"_138":25,"_38":154,"_13":155,"_33":34,"_35":37,"_24":25,"_142":156,"_27":157},{"_43":144,"_32":145,"_30":146,"_136":-5,"_41":42,"_40":147,"_138":25,"_38":148,"_13":149,"_33":150,"_35":151,"_24":25,"_142":-5,"_27":152},{"_43":133,"_32":134,"_30":135,"_136":-5,"_41":42,"_40":137,"_138":25,"_38":139,"_13":140,"_33":34,"_35":141,"_24":25,"_142":-5,"_27":143},"fb2379d8-b37e-4daa-b925-23a1043ff25e","askaoaoa_page.ts","9af845d6-871c-11f1-bcc1-1607ee4eb77e","parentId",63,"latest",["D",1784869322686],4,"// AskAOAOA — PAGE val (Val Town Script val, Unlisted).\n// Holds the web frontend (generated from askaoaoa-assistant.html). The web val imports this via PAGE_URL.\n// Regenerate this file when the frontend changes, then re-save the web val.\nexport const PAGE =\n '\\n\\nAskAOAOA \\u2014 Aryan Opulence Community Assistant\\n\\n\\n\\n\\n

\\n

Aryan Opulence \\u00b7 AOAOA

\\n

AskAOAOA

\\n

Enter your flat number to continue.

\\n\\n\\n

\\n

\\n\\n

\\n

Ask, suggest, or raise an issue.

\\n

Ask anything about our bye-laws and rules and I\\'ll explain in plain words. You can also suggest an improvement for the community, or escalate an unresolved issue to the Managing Committee \\u2014 just tell me in plain words.

\\n

Try asking

\\n

\\n\\n\\n

\\n\\n

AI-generated \\u2014 replies can be imperfect; please verify anything important with the Managing Committee. Answers reflect the association\\'s official documents only and aren\\'t legal advice. Where a bye-law conflicts with the Act, the Act prevails.

\\n

About this assistant

\\n

Release notes

\\n\\n

\\n

About AskAOAOA

\\n\\n

\\n

AskAOAOA is a resident-built assistant for the Aryan Opulence community. It answers questions from the association\\'s own official documents \\u2014 the registered bye-laws, the Rule Book, and the Party Hall and Parking rules \\u2014 and explains them in plain words.

\\n

You can also suggest an improvement, share feedback or a concern, or escalate an unresolved MyGate issue to the Managing Committee. Anything shared this way is recorded privately for the committee only \\u2014 never made public.

\\n

It works in English, \\u0939\\u093f\\u0902\\u0926\\u0940 and \\u0c95\\u0ca8\\u0ccd\\u0ca8\\u0ca1, on both the web and WhatsApp.

\\n

You can also ask for \\u2014 and share \\u2014 recommendations for anything nearby \\u2014 a dentist, hospital, hardware shop, restaurant, hotel, plumber, tutor, and more \\u2014 shown with the neighbours who vouch for them.

\\n

How it works: it uses an AI model restricted to the association\\'s documents, so answers stay grounded in what the community has actually adopted. Replies are AI-generated and can occasionally be imperfect, so please confirm anything important with the Managing Committee.

\\n

Built by Shyam A Nair (602-C), as a community volunteer effort.

\\n

\\n\\n';","label",[134],"06753949-6f22-4552-8f0d-ee4885ab0c54","askaoaoa_data.ts","98ea1bc8-79fe-11f1-a4d2-1607ee4eb77e",56,["D",1784818222591],6,"script","// AskAOAOA — bye-law DATA val. Holds the knowledge the assistant answers from.\n// To add a document later: add an entry to the DOCS list below, then Save.\n// The main AskAOAOA val imports SYSTEM from here (set its DATA_URL env var to this val's module URL).\n\nconst BYELAWS = `\nARYAN OPULENCE APARTMENT OWNERS' ASSOCIATION (AOAOA) — BYE-LAWS\nRegistered under Karnataka Apartment Ownership Act, 1972 (KAOA) & Rules 1974. Reg. no. BK-I BNG-BMH 3607/2023-24. Complex has 189 units across Blocks A, B, C, D. Office: Aryan Opulence Apartments, Dr. Vishnuvardhan Road, Srinivasapura, next to Shell Petrol Bunk & Ambrosia, Bangalore-560060. Drafted by Adv. Beena P.K., Nextlegal Services.\n\nCHAPTER I — TITLE, DEFINITION, OBJECTS, MEMBERSHIP\n1. SHORT TITLE & APPLICATION. 1.1 Called \"Bye-laws of The Aryan Opulence Apartment Owners' Association\". 1.2 Apply to all owners and residents. 1.3 All present/future owners, tenants, future tenants, their employees or anyone lawfully entitled to use/enter the facilities are subject to these bye-laws. 1.4 Mere acquisition, renting, taking on license or occupancy of any unit signifies these bye-laws are accepted and will be complied with.\n2. NAME & ADDRESS. 2.1 Name: \"Aryan Opulence Apartment Owners' Association\", short AOAOA. 2.2 Office working hours 9:00 AM to 5:00 PM, Monday to Saturday except public holidays. 2.3 Bye-laws come into force from date of registration of the Association.\n3. DEFINITIONS. 3.1 ACT = Karnataka Apartment Ownership Act 1972 & Rules 1974. 3.6 MANAGEMENT/EXECUTIVE COMMITTEE = duly constituted members, all of whom shall be apartment owners residing in the complex, elected in a General Body Meeting. 3.9 COMMON AREAS & FACILITIES include: land; foundations, walls, roofs, halls, corridors, lobbies, stairs, fire escapes, entrances; basements, gardens, children's play area, storage; offices, security room, restrooms; central services (power, light, gas, hot/cold water, heating, AC, borewells); elevators, tanks, pumps, motors, cable/internet, security equipment; Club House, Swimming Pool, Sitting Lounge, Gymnasium, Multipurpose Party Hall, Sports Arena, Cricket Nets, Basketball Court, Shuttle Badminton. 3.10 CORPUS FUND = fund for non-recurring/emergency major repairs or redevelopment; kept in nationalized/scheduled bank fixed deposits; interest used for emergency works or as decided in AGM/SGBM. 3.11 DEEMED MEMBER: (i) sole owner — spouse/parent/legal heir/successor above 18 authorized by Power of Attorney; (ii) joint owner arrangements; (iii) company/firm may nominate a director/partner/authorized rep via PoA or Board Resolution for meetings and proxy voting. 3.12 DEFAULTING MEMBER = any owner who has not paid dues for Three months or more; not entitled to any rights, privileges, services or facilities of the Association; forfeits all voting rights and contesting elections until all dues cleared. 3.14 FINANCIAL YEAR = April 1 to March 31. 3.15 MAJORITY = 51% or more of votes of members present. 3.16 MAINTENANCE CHARGES = charges payable quarterly or as prescribed per apartment; used for elevators, round-the-clock security, cleaning, water supply, common-area electricity, plumbing, electrical & sanitary services; determined by Managing Committee with approval of Association. 3.18 RESIDENT = owner, family of owner, or tenant in occupation via a legally valid document (lease/rental/leave & license). 3.19 RESTRICTIVE COMMON AREA = store rooms, overhead tanks & water sump, terrace, transformer area, LT distribution panel room, DG set area, common floor ducts, Water Treatment Plant, Sewage Treatment Plant room, etc.\n4. OBJECTS. To act as the association; invest/deposit funds and maintain/repair/replace common areas; provide a secure, healthy, harmonious environment; enforce bye-laws uniformly; manage common areas as custodian (incl. maintenance & repairs, upkeep of amenities, consumables, annual external inspection & colour washing, servicing/insurance against fire & earthquake of motors/pumps/lifts); frame rules with Association approval; arrange recreational/sports/educational activities; rent common areas for social non-commercial purpose with Association consent; sue/defend legal proceedings related to common areas & bye-law enforcement; foster fellowship; not act beyond its objects without amending the bye-laws.\n5. MEMBERS. 5.1 All who purchased/acquired an apartment become members from taking possession; company/Trust/HUF/Firm — authorized rep becomes member; membership not to exceed number of apartments owned; file a Declaration; pay non-refundable entrance/membership fee; a family/company/firm counts as one Unit, but owning more than one apartment gives membership equal to number owned. 5.2 On proposed change of ownership, transferor submits transfer document, surrenders membership card, tenders dues, and gets a NOC. 5.3 New purchaser submits ownership document and pays non-refundable entrance fee. 5.4 JOINT OWNERS: jointly entitled; only one owner approved by the others is the representative; that name entered in register; where more than two joint owners, on death the surviving joint owner(s) may become member with certified death certificate. 5.5 Each member provided a copy of bye-laws on request; member is responsible for ensuring all residents/tenants are aware of and adhere to the bye-laws. 5.6 To rent/lease, member must inform Managing Committee in writing from registered email and submit Know Your Tenant (KYT) document — name, photo, contact number, emergency contact, email — of all tenants; KYC for company/entity tenant. 5.7 On death, membership transfers per Will or to legal heirs; for a minor legatee the guardian's name is entered; no membership fee during such transfer. 5.8 (i) Transfer by Sale Deed: seller ceases to be a member; purchaser and seller must obtain a No Dues Certificate; if sold without it, onus is on purchaser to pay outstanding dues before becoming a member. (ii) Transfer by Gift/Will/Relinquishment to spouse/parent/child/donee/legal heir: transferee automatically eligible for membership.\n6. CESSATION OF MEMBERSHIP. 6.1 On selling/transferring (single unit holder). 6.2 Dying intestate: (i) sole — to legal heirs; (ii) joint — to surviving joint owner; (iii) more than two joint — to any one surviving owner with consent of others. 6.3 Dying testate — to beneficiaries per Deed of Will.\n7. DISQUALIFICATION TO STAND OR VOTE. 7.1 No owner/member may vote in any election or stand for any Managing Committee office if in arrears of any dues for more than 90 days as on the date of the concerned meeting. 7.2 A member convicted by a court for any offence involving moral turpitude is not eligible to contest. 7.3 Any office bearer/MC/sub-committee member found guilty of financial impropriety, defalcation, corruption etc. ceases to be an MC/sub-committee member for not less than two years; overdue payments attract an extra 12% penalty per annum; opportunity to explain given; domestic enquiry conducted; recommendations approved by the Association.\n\nCHAPTER II — MANAGING COMMITTEE\n8. The Managing Committee governs the affairs of the Association in conformity with the decision of the majority of members.\n9. MANAGING/EXECUTIVE COMMITTEE. 9.1 Office bearers: President, Vice-President, Secretary, Joint Secretary, Treasurer, Joint Treasurer, and Seven Executive Members. The MC comprises Four representatives from Block A, and Three each from Blocks B, C and D. 9.2 MC empowered to frame procedural rules/sub-rules/handbook/SOPs to these bye-laws with the approval of the Association (in AGM or SGM); no such rules may contradict the bye-laws.\n10. SPECIAL/SUB COMMITTEE. 10.1 May be formed to support the MC; volunteers may be owners and/or residents, approved by the MC. 10.2 Must be invited to the MC meeting where their reports are discussed.\n11. ELECTIONS. 11.1 All elections by secret balloting. 11.2 Only members (owners) eligible to contest; Thirteen (13) MC members are elected by the members; the elected members then elect office bearers among themselves. 11.3 An Office Bearer shall not hold office consecutively for more than one term; if there is no new nomination for a post, the existing office bearer may be given the option to continue with Association approval. 11.4 No canvassing/campaigning for votes; no money to be spent by contestants; violation = disqualification and the election nullified. 11.5 Representation by women shall be encouraged. 11.6 Process: (i) President calls elections via GBM, conducted by secret ballot; (ii) MC nominates an Election Officer plus 2–3 volunteers (not candidates) with Association approval; (iii) candidates listed in alphabetical (English) sequence on ballots; (iv–v) Election Officer conducts the election by secret ballot, calls & scrutinises nominations, announces results; (vi) No MC member is eligible for election for more than one term of one year; eligible for re-election after a gap of one term (one year); (vii) owners may self-nominate for one post; (viii) if no nominations by the cut-off, the vacancy may be filled by an Association nominee from resident owners; (ix) Election Officer publishes plan for nominations/process/results, communicated via notice boards and email; (x–xvi) scrutiny with MC, final candidate list, secret ballot if contested, objections referred to and decided finally by the Election Officer, simple majority required for each office, a tie is resolved by mutual withdrawal or the candidate senior by age (per birth certificate), results declared & recorded by the Election Officer and shared with President and Secretary.\n12. VOTING. 12.1 Each apartment owner has one vote; an owner of multiple apartments has votes equal to the number of apartments. 12.2 Casting where owned by: Trust — a trustee authorized by other trustees; Firm — a partner authorized by other partners; Company — a director/officer authorized by Board resolution; Joint Owner — the representative approved by the other joint owners. 12.3 Vote in person, by email, or by proxy; the proxy must be a resident of the complex, authorized by the owner in writing in the prescribed form, and lodged with the secretary/president/electoral officer not less than 48 hours before the GBM/elections; no person may be proxy for more than 2 votes. 12.4 Voting by secret ballot, email, or online voting through platforms such as Apartment Adda, Common Floor. 12.5 A proxy authorization letter must be submitted 48 hours before the polls. 12.6 No member may stand for MC election if in arrears of contributions for common expenses & Corpus for more than 90 cumulative days, or has defaulted by delayed payments on three or more occasions over three years.\n13. SUITS BY AND AGAINST THE ASSOCIATION. The Association may sue and be sued in its name represented by any MC member; cases instituted with Association approval; non-payment matters may be taken up by the MC.\n\nCHAPTER III — OFFICERS\n14. THE PRESIDENT. 14.1 Presides over all MC meetings, the AGM and special meetings; supervises whether work is done per resolutions. 14.2 Subject to MC approval, may take actions against any person acting against the interest of the Association; may defend/pursue legal actions, enter contracts, sign documents. 14.3 Operates bank account(s) jointly with the Treasurer or the Secretary. 14.4 In the President's absence the Vice-President presides; if both absent, the Secretary. 14.5 In case of a tie, the President has a casting vote in addition to their own. 14.6 Enters contracts upon approval of MC members.\n15. THE VICE-PRESIDENT. Assists the President and is deemed Acting President in the President's absence.\n16. THE SECRETARY. 16.1 Carries out all business per rules. 16.2 Keeps the Minutes of MC and Association meetings; custodian of books of accounts, references, articles, furniture. 16.3 Arranges MC meetings with the President's permission; arranges GBM/SGBM; maintains registers & accounts. 16.4 In the President's absence, may defend/pursue legal actions. 16.5 Keeps documents/registers/records in safe custody; maintains a register of Owners and Residents. 16.6 Power to appoint or remove staff subject to MC approval. 16.7 Circulates minutes of all GBM/SGBM to all owners.\n17. THE JOINT SECRETARY. Assists and acts for the Secretary in the Secretary's absence.\n18. THE TREASURER. 18.1 Responsible for monitoring funds & securities and keeping full accurate accounts of receipts, disbursements, assets, liabilities. 18.2 Custodian of the cheque book; prepares cheques; in the President's absence the Treasurer with the Secretary can operate the bank account. 18.3 Maintains books, verifies the balance sheet, monitors funds in consultation with MC; custodian of books & assets. 18.4 Issues receipts & payment vouchers, maintains copies; maintains petty cash with MC consensus. 18.5 Liaises with the Auditor for the audit.\n19. THE JOINT TREASURER. Assists and acts for the Treasurer in the Treasurer's absence.\n20. THE EXECUTIVE MEMBERS. 20.1 Elected members of AOA in the MC. 20.2 Elected for one term. 20.3 Assist/support decision making per MC instructions. 20.4 Head specific committees. 20.5 May co-opt volunteers.\n21. SPECIAL COMMITTEE. 21.1 MC may constitute special/sub committees for identified areas. 21.2 Each has one MC member as chairperson as far as possible. 21.3 MC oversees and reserves the right to govern or dissolve such committees.\n22. TENURE OF OFFICE BEARERS. Maximum one year from date of election; may be extended with Association consent; fresh elections begin at least Two months before expiry of the existing term.\n23. HANDING OVER OF CHARGE. Outgoing Secretary/Joint Secretary and Treasurer/Joint Treasurer hand over records, documents, books of accounts and cash per the updated book of accounts to their incoming counterparts; the outgoing MC hands over charge within 30 days of appointment of the new MC.\n\nCHAPTER IV — ADMINISTRATION\n24. PASSING OF RESOLUTIONS. All resolutions of the MC and GBM/SGBM are passed by simple majority; in a tie the President has the casting vote.\n25. QUORUM. 25.1 51% of the total members present constitutes a quorum for GBM/SGBM; if no quorum, those present (not less than an hour) may adjourn, and at the adjourned meeting business may be transacted with the members present and is binding. 25.2 Proxy/nomination by proxy in prescribed format, may be sent by email from the registered id; applicable for one GBM only; separate proxies may be issued for each GBM. 25.3 Quorum for a Managing Committee meeting is 50%; decisions of MC members present are valid if passed by majority.\n26. NOTICE OF THE MEETING. AGM notice sent by the Secretary (or Joint Secretary) stating purpose, agenda, date, time, place to each member at last known address/email at least 21 days before, and displayed on the notice board or via WhatsApp/Email. SGBM notice at least 7 days before. Mailing/emailing/display counts as served. Along with each AGM notice (after the first), audited financial statements of the immediately preceding financial year and a proxy form are also sent.\n26(Powers). POWERS AND DUTIES OF THE ASSOCIATION. 26.1 Responsible for administering the complex, approving the annual budget, establishing & collecting monthly assessments; resolutions require approval by a majority of owners voting in person or proxy and are binding. 26.2 Day-to-day affairs carried on by the MC, which may assign responsibilities to a Manager/employees. 26.3 FORCE MAJEURE: the Association is not responsible for any loss to members on account of earthquake, flood, fire, riots, pandemic, epidemic, acts of God, or loss caused by any wilful act or negligence of a member.\n27. PLACE OF MEETINGS & ONLINE MEETINGS. 27.1 Meetings held at a convenient place, preferably within Aryan Opulence precincts. 27.2 AGM, SGBM and MC meetings may be conducted online on acceptable platforms; online presence counts as presence in person; the Association may still insist on personal appearance where appropriate.\n28. CHAIRPERSON OF THE MEETING. The President chairs; in absence the Vice-President; if both absent, the Secretary.\n29. ANNUAL GENERAL BODY MEETING. First AGM within three months of registration; thereafter the annual meeting within three months of the close of the financial year each year; principal officers elected preferably by ballot; the MC stays in office until the conclusion of the next GBM and handover.\n30. DUTIES OF THE GENERAL BODY. 30.1 Guide the association. 30.2 Frame/decide policy. 30.3 Elect MC members. 30.4 Approve annual budgets. 30.5 Appoint the statutory Auditor. 30.6 Approve audited accounts of the previous FY. 30.7 Transact other necessary business.\n31. SPECIAL MEETING. The President must call an SGBM when directed by an MC resolution or on a petition signed by not less than 30 members; notice stating date/time/place/purpose issued at least 7 days before and convened within 30 days of receipt of the written request; no other business transacted; quorum same as the AGM.\n32. ORDER OF BUSINESS. 32.1 Roll call & record of proxy. 32.2 Reading of the agenda. 32.3 Reading & confirmation of minutes of the preceding meeting. 32.4 Reports of sub-committees. 32.5 Adoption of audited accounts with Auditor's & Treasurer's reports. 32.6 Adoption of budget for the following quarter. 32.7 Amendments to the Rules & Bye-laws. 32.8 Moving of resolutions & voting. 32.9 Election of office bearers & MC (in the last meeting of the FY). 32.10 New business with the Chair's permission. 32.11 Q&A session. 32.12 Vote of thanks.\n33. POWER AND DUTIES OF THE MANAGING COMMITTEE. Constituted for proper maintenance & administration; has the powers & duties necessary for that, to work in the best interest of members.\n34. OTHER DUTIES. 34.1 Care, upkeep, maintenance and surveillance of the complex, common and restricted areas, party hall, security office, swimming pool. 34.2 Collect payments, pay service providers, prepare next year's budget. 34.3 Designate/employ/remunerate/terminate necessary personnel. 34.4 Sanction working expenses, grant cash advances, verify cash balances (with Association approval if required). 34.5 Receive & deal with complaints/grievances. 34.6 Inspect records of Secretary & Treasurer. 34.7 Recover all sums due. 34.8 Make payments to Government/Semi-Government bodies. 34.9 Ensure a maintenance agreement with suitable agencies. 34.10 Supervise records of maintenance agencies. 34.11 Advise on accounts procedure & audit periodicity. 34.12 Full authority to increase/decrease number of labour/salary per budget or Minimum Wages Act. 34.13 Define a transparent SOP for procurement of materials & services. 34.14 Implement any government-mandated SOP for unanticipated circumstances (e.g. a Pandemic). 34.15 Keep a check on compliance with statutory requirements.\n35. MANAGER OR SUPERVISOR. MC may employ a Manager/Supervisor and subordinate workers with Association approval; may remove/dismiss/suspend an employee after giving reasonable opportunity to defend and recording reasons; the preferred option is an outsourced agency/hire basis, with direct employment only on specific GBM approval.\n36. VACANCIES. On a vacancy due to ineligibility/non-resident status/resignation/death, or when an MC member sells the unit: 36.1 the MC may nominate/co-opt any member with Association consent for the remaining term; 36.2 shall fill vacancies caused by reasons other than removal by vote of the Association.\n37. REMOVAL OF MEMBERS OF THE MANAGING COMMITTEE. 37.1 At an AGM/SGBM with the required quorum, any MC member may be removed by a resolution passed by a 2/3 majority of the members, and successors elected; a member whose removal is proposed for financial impropriety/defalcation/corruption (not for personal agenda) must be given an opportunity to be heard; a person so removed is not eligible to contest MC election for six years from removal. 37.2 An MC member who fails to attend 3 successive meetings without proper cause and intimation ceases to be an MC member (MC uses discretion, records it in the minutes, and notifies in writing).\n38. ORGANIZATION OF MEETING OF THE MC. The first meeting of the newly elected MC is held within 10 days of election at a place fixed by the President; no notice is necessary; a majority of the MC must be present.\n39. REGULAR MEETINGS OF THE MC. 39.1 Held on such date/time/place as a majority determine; at least one meeting each quarter (or fixed permanently for the year); notice at least three days prior by email or phone. 39.2 The Secretary/Joint Secretary maintains minutes recorded within 3 days.\n40. SPECIAL MEETINGS OF THE MC. Called by the President with three days' notice; proceedings included in the agenda of the subsequent ordinary MC meeting for ratification.\n41. EMERGENCY MEETINGS OF THE MC. Convened by the President (or Vice-President in the President's absence) without formal notice, giving sufficient justification; all decisions ratified at a Special/Ordinary MC meeting within 15 days.\n\nCHAPTER V — RIGHTS AND OBLIGATIONS OF OWNERS/MEMBERS\n42. ASSESSMENT. 42.1 All owners obliged to pay maintenance charges by the due date; MC empowered to collect interest/penalty at rates it decides. 42.2 Amounts for exceptional/unanticipated expenses collected as the MC determines; common expenses payable by all owners. 42.3 The MC may adopt all legally available methods to collect; may publish a list of defaulters (amounts overdue and interest/penalty) on the notice board; in suitable cases may curtail or deny one or more common facilities to defaulters, but only after giving them an opportunity to explain within 14 days of notice. 42.4 If there is no credit/deposit in the owner's account, suitable action including legal action may be taken with penalty, and common facilities may be suspended. 42.5 Arrears plus penalty become a charge on the apartment; if the owner transfers the property, the charge binds the transferee. 42.6 Arrears unpaid beyond the published due date carry a penalty per month/part thereof, as the MC decides. 42.7 Maintenance charges are paid by all owners whether the unit is occupied or vacant; if a resident (tenant/lessee/licensee) is put on the onus and fails to pay, the ultimate responsibility is on the owner. 42.8 Assessment made pro-rata by the area of the apartment vis-à-vis total area, with a fixed component if necessary; unpaid, services may be forfeited.\n43. MAINTENANCE CHARGES. 43.1 Published by the MC Quarterly after reviewing the financial statement and prevailing cost of service. 43.2 Components: COMMON CHARGES (AMC for elevators, generators, outdoor play area, STP, WTP, ACs in gym & party hall, security room, swimming pool, borewells, water pumps; service expenses for estate manager, electrician, plumber, lift man, housekeeping, security guards, garden maintenance, garbage disposal); CONSUMABLES & MAINTENANCE (lighting, fans & ACs in common areas, day-to-day consumables); COMMON BILLING (electricity for common areas & utilities, water bill, building insurance, maintenance software). 43.3 Expenses & assessments on a pro-rata basis, i.e. amount per square foot multiplied by the super built-up area of each apartment. 43.4 Ad-hoc payments for major expenses (replacement of lift/generator, building painting) paid by the due date fixed by the MC. 43.5 The Corpus Fund shall NOT be used for regular maintenance; any use requires Association approval. 43.6 Interest on arrears at a rate decided by the Association from time to time. 43.7 Payments via internet/online banking/cheque; payment reference number shared for reconciliation; NO payments accepted in cash; a dishonoured cheque attracts a penalty (Association-decided per cheque or actual bank penalty, whichever is more). 43.8 After intimation of the amount, a maximum of Ten working days is given for payment; after the grace period, a late fee (Association-approved) applies; dues/delay exceeding one month attract both a late fee and penal interest. 43.9 Non-payment of dues for 3 months or over is just and sufficient reason for the MC to deny use of any or all facilities/services, provided due written notice of not less than fifteen days is given (by email/electronic/social media or registered post; if not accepted, affixed to the main door and put on the notice board); after 15 days from posting, the Association may initiate action.\n44. MAINTENANCE AND REPAIRS. 44.1 Every member must promptly perform all maintenance/repair within their own unit; if not done and it affects others, the defaulting owner is responsible for damages; no alteration/modification affecting the facade, main structure, or common walls/floors between units. 44.2 Where improvements inside an individual apartment are necessary for the proper maintenance of common service lines, owners must implement them; the expense is borne by the Association and endorsed by the MC. 44.3 All repairs of inner installations (water, light, gas, power, sewage, telephones, ACs, sanitary, doors, windows, lamps and other accessories) are the responsibility and at the expense of the apartment owner. 44.4 No member/resident shall object to work in the common interest even if it causes inconvenience. 44.5 No member/resident may make any modification/alteration/major repair within the apartment or on installations without notifying the Association in writing through the President/Vice-President/Secretary and receiving approval. 44.6 Every member reimburses the Association for expenditure repairing/replacing damage caused through their fault. 44.7 For inter-apartment seepage/leakage (except inherent construction defect), the MC after consulting experts fixes responsibility in consultation with the owners concerned, who repair it; the MC decision is final and binding. 44.8 Owners sharing a ceiling/floor/wall should co-operate to repair seepage/leakage; the cost may be shared appropriately by both owners. 44.9 Liability, rights, interest, benefits and privileges in common areas are shared equally by all owners.\n45. USE OF UNITS AND INTERNAL CHANGES. 45.1 All units for residential purpose only; owners must exercise extreme caution in letting out and are responsible for any nuisance/problems created by their tenants. 45.2 No structural modifications/alterations are allowed in the apartment unit. 45.3 Illegal activities, and storing hazardous/combustible substances (chemicals, explosives, gases excluding cooking gas), radioactive materials, heavy objects, or any objectionable activity, are strictly prohibited. 45.4 Every owner must inform the Association in advance of a change in occupancy; for movement of household goods a shifting fee (decided by MC with Association approval) is levied per occasion to cover repairs/security/housekeeping; the owner/resident must take care not to damage lifts or common areas; cost of major damage is charged to the owner. 45.5 An owner renting/leasing must follow the process prescribed by the police and law-enforcement; the Association is not responsible for violations by the owner/resident.\n46. RIGHT OF ENTRY AND USE OF COMMON AREAS. 46.1 A resident must grant right of entry to the Manager or authorized person in an emergency, whether the owner is present or not. 46.2 The resident must permit repair agencies to enter for repairs on 24 hours' advance request at a convenient time; entry is immediate in an emergency. 46.3 To control noise pollution, the working hours of carpenters/masons/handymen are regulated; interior work on all working days is 9:00 AM to 5:00 PM and is to be avoided on Sundays or festival days as fixed by the MC. 46.4 The main gate entry is kept locked between 11:00 PM and 5:00 AM; it may be opened for residents; visitors are allowed during this period only after being identified by the resident or with prior approval. 46.5 No furniture/packages/objects (bicycles, clothes stands, flowerpots) may be placed in lobbies, vestibules, stairways, elevators, terrace or parking bays; such areas are only for transit. 46.6 Elevators are for owners/residents and their guests only. 46.7 No construction/storage in vehicle parking; parking is only for light motor vehicles and two-wheelers of residents, parked in the allotted area; cross-parking is strictly prohibited; commercial vehicles are not allowed in the basement or ground floor and may use visitors' parking only for loading/unloading.\n47. RULES OF CONDUCT AND OCCUPATION. 47.1 No advertisement/hoarding/notice/poster in the premises except as authorized by the MC. 47.2 Residents must exercise extreme care about noise (musical instruments, radios, TV, amplifiers); beyond 11:00 PM refrain from noise likely to disturb neighbours. 47.3 No throwing garbage/trash outside the disposal installations or through windows/balconies; segregate waste into dry/wet and reject (sanitary/bio-medical); e-waste at designated areas only; non-compliance may lead to waste not being picked up and other penal action. 47.4 Garbage disposal per Association/Government process; violation attracts penalty. 47.5 No dusting rugs from windows/balconies; clean rugs/car seats carefully so surrounding walls/pillars are not defaced. 47.6 Children play only at allotted places. 47.7 No subletting for commercial use or sharing an apartment for additional monetary benefit; no apartment rented as a service apartment/customary hotel/PG accommodation; units for residential purpose only. 47.8 Staff employed by residents must bear good character and be registered with the Association per the prescribed process. 47.9 No wiring for electrical/TV/intercom protruding through exterior walls/roof except as authorized; MC decides location/placement of external units. 47.10 No member/resident may install machinery/equipment such as generators in common areas. 47.11 Drive at the specified speed; follow \"Stop and Proceed\"; avoid using the horn, especially between 10:00 PM and 6:00 AM. 47.12 Common areas like the party hall/kids' play area must be left clean & tidy after use; garbage disposed at the collection point; damage/defacement compensated by the user. 47.13 The Club House/Party hall may be booked for private ceremonies (if available) by paying prescribed charges decided by the MC; left clean; damage compensated by the user. 47.14 Every member bears the cost of all repairs to internal installations of their apartment. 47.15 Conducting processions or religious functions in common areas, and erecting pandals/shamianas, is not permitted in common areas unless authorized by the MC; such functions are conducted at the designated place; usage charge (if any) decided by the Association and paid in advance. 47.16 Every member/resident must respect other owners' rights and cause no inconvenience; misbehavior/nuisance attracts severe punitive action. 47.17 No member/resident may occupy any portion of a common area without written MC permission; the MC may grant occupation for short periods for marriages/social functions at its discretion without obstructing vehicular movement, provided the premises are released in the same condition and the cost of cleaning/repair is borne by the user. 47.18 No owner/resident may engage any staff of the Association for their private purposes. 47.19 No member/resident may threaten/abuse/reprimand/assault or in any way engage with Association staff, but may report misbehavior/neglect in writing to the MC. 47.20 Residents are responsible for the behavior and actions of their visitors and for the cost of any damage they cause. 47.21 Possession/use of illegal drugs or abuse of prescription drugs within the complex will not be tolerated and may result in police involvement. 47.22 Animal sacrifice/slaughtering and disposal of animal waste in common areas is strictly prohibited. 47.23 Smoking and alcohol consumption inside the complex, other than inside the residential unit, is strictly prohibited — not allowed in common areas, verandahs, staircases, terrace, courtyard, swimming pool area, party hall, children's play area, parking area, Association office and other restricted areas. 47.24 Residents keeping pets must abide by municipal bye-laws and other regulations and ensure the pets cause no nuisance; pets must not be left unattended or allowed to commit nuisance in common areas (pathways, lawns, free space); the owner must clean up. 47.25 Unaccompanied and unleashed pets are not allowed inside lifts or the premises; pets must not be brought to the party hall, swimming pool area, or park/gardens/play areas. 47.26 The MC reserves the right to issue any reasonable restrictions beyond the above with Association approval.\n48. COMMUNITY EVENTS AND FUNCTIONS. 48.1 Fund raising for any function/event is the prerogative of the MC only; the MC sets aside a budget and additional expenses are raised only through sponsorship. 48.2 Independence Day, Republic Day, Gandhi Jayanti, Children's Day and Rajyotsava Day are official functions of the Association.\n49. GRIEVANCE OR COMPLAINTS. Members must file complaints/grievances only in writing addressed to the Association; these are discussed in MC meetings and decisions/actions conveyed to complainants; the MC decision is final and binding.\n\nCHAPTER VI — FUNDS AND INVESTMENTS\n50. FUNDS. Mobilized by the MC with Association approval via: 50.1 contributions/deposits/donations from owners/others; 50.2 surplus of income over expenditure; 50.3 maintenance charges & contingency funds; 50.4 sale of scrap/compost/dry waste; 50.5 loans raised for a specific purpose if necessary; 50.6 rent/license charges for common areas/party hall; 50.7 charges on movement of household articles / move-in-out and debris charges; 50.8 sponsorship/marketing/advertisement income; 50.9 fee on transfer of membership; 50.10 penalties for rule violations; 50.11 any other approved means.\n51. INVESTMENTS. 51.1 Fixed deposit in nationalized/scheduled banks. 51.2 Any other lawful manner approved by the Association.\n52. AFFILIATION. The Association may join a federation of Associations of Apartment Owners and pay the contribution.\n53. ACCOUNTS. 53.1 Bank account opened in the Association's name; all moneys deposited; the Treasurer may retain a fixed petty-cash amount; any payment above a fixed amount by cheque or bank transfer only. 53.2 Within three months of FY close, prepare and get audited: Income & Expenditure Account, Receipt & Payment Account, Balance Sheet & Profit and Loss Account. 53.3 The audited statement is open to inspection by any member during office hours; a copy submitted to the competent authority not later than 1st July every year. 53.4 The Treasurer provides a monthly due statement to the MC.\n54. APPOINTMENT OF AUDITORS. The Association appoints an independent Chartered Accountant (who does not own an apartment in the complex) in the GBM; term of one year at a time.\n55. INTERNAL AUDITOR. The Association may nominate an internal auditor/committee from owners/members/deemed members, or appoint an external firm, reporting only to the MC; the internal auditor is not an MC member; the service is honorary (no remuneration); term one year; performs monthly audit of expenses.\n56. POWER OF AUDITOR. Entitled to call for and examine all books and related documents; may make a special report to the Association.\n57. APPOINTMENT OF CONSULTANT, ARCHITECT AND AGENCIES ON CONTRACT BASIS. The MC may, by resolution, appoint/engage legal consultants, architects, accountants, civil/engineering contractors for maintenance/repair/replacement and fix their remuneration and contract terms, with the approval of the GBM.\n58. MORTGAGE, LEASE AND SALE. An owner who mortgages a unit notifies the Association in writing through the Secretary/President with the mortgagee's name and address; the Association maintains a \"Mortgages of Units\" book.\n59. NOTICE OF UNPAID ASSESSMENTS. At the request of a mortgagee, the MC reports any unpaid assessment due from the owner; the mortgagee must pay such dues to the Association before affecting the mortgage.\n60. REGULATIONS, RULES AND ADMINISTRATIVE PROCEDURE. The Association frames rules/regulations/procedures for administration and to prevent unreasonable/improper use of facilities; these may be amended or supplemented by the GBM or a Special meeting.\n\nCHAPTER VII — COMPLIANCE\n61. COMPLIANCE. These bye-laws comply with the Karnataka Apartment Ownership Act, 1972; in case any bye-law conflicts with the Act, the provisions of the Act apply.\n62. SEAL OF THE ASSOCIATION. A common seal in the custody of the Secretary/Joint Secretary, used only under the authority of an MC resolution; every deed to which it is affixed is attested by two MC members and the Secretary/Joint Secretary or authorized person.\n\nCHAPTER VIII — AMENDMENT\n63. PROVISION FOR AMENDMENT. Bye-laws may be amended by the Association at a duly constituted GBM convened for the purpose; no amendment takes effect unless approved by at least 75% of the total members present and voting in person, provided the meeting is valid with the required quorum; subject to such amendments being approved by the statutory authority.\n64. PENALTY FOR BREACH OF RULES. The MC may prescribe penalties, with the consent of the Association, for breach of the rules by owners/residents.\n65. SAVING CLAUSE. While the Association takes every step to maintain peace, safety and security, neither it nor its office bearers are held responsible for untoward incidents due to negligence or wilful acts of residents; residents are fully responsible for acts beyond the control of the Association. In any contradiction/ambiguity in the bye-laws, the construction in favour of the objectives of the Association prevails.\n66. INDEMNITY. 66.1 Every office bearer, MC member and sub-committee member (past or present, incl. AOAOA) is indemnified by the Association against third-party claims connected with any contract/deed entered in due discharge of duty, unless gross negligence/fraud is found; such claims are contested by the MC. 66.2 Litigation is to be avoided as far as possible and mediation encouraged. 66.3 No office bearer/MC/sub-committee member (past or present) is liable for acts/omissions/defaults in good faith unless gross negligence/malafide/fraudulent intention is found.\n67. PROVISIONS FOR DISSOLUTION. 67.1 Dissolution is intended only under the extraordinary contingency where the complex is damaged beyond use and cannot be restored. 67.2 The Association is dissolved when members holding 2/3 of voting rights decide so at a general meeting specifically convened, casting votes in person/proxy. 67.3 Remaining property/assets, after satisfying debts & liabilities, are distributed among members proportionately by the super built-up area of each apartment; if it cannot be divided, it is sold and proceeds distributed proportionately, appointing a liquidator if needed. 67.4 Any dispute among the MC and/or members on dissolution is referred to the principal court of the district jurisdiction where the registered office of the Association is situated.\n`;\n\nconst NAME = \"AskAOAOA\"; // change this one line to rename the assistant\n\n/* -------- documents the assistant can answer from --------\n To add a document later: copy the commented block below, give it a\n title, an optional ref (date/status), and paste its full text into\n content. Nothing else needs to change. */\nconst DOCS = [\n {\n title: \"Bye-Laws of the Aryan Opulence Apartment Owners' Association\",\n ref: \"Registered, Reg. 3607/2023-24, under KAOA 1972\",\n content: BYELAWS,\n },\n {\n title: \"AOAOA Rule Book\",\n ref: \"Version 02, 15 Aug 2023; supplements the registered Bye-Laws\",\n content:\n `AOAOA RULE BOOK, Version 02, dated 15 August 2023. Supplements the registered Bye-Laws. Precedence: if the Bye-Law and the Rule Book differ on a policy matter, the Bye-Law prevails; topics not covered in either are decided by the Managing Committee (MC) case-by-case.\n\nA. ADMINISTRATION\nSection 1 Cancellation of Resolution: An SGM resolution cannot be cancelled by a later SGM resolution until 6 clear months after the original. A point not discussed for want of quorum cannot be raised again in a subsequent SGM until 6 months from the original meeting.\nSection 2 Order of Business: as per Section 32 of the Standard Bye-Law; at AGMs also act on Secretary/Auditor reports, adopt the budget, deal with appeals against the MC, assess maintenance charges, and review the defaulters list and action.\nSection 3 Circulars: the MC issues binding circulars (rules/policies) and may act against non-compliance.\n\nB. FUNDS AND ACCOUNTS\nSection 4 Funds Utilisation: capital goods above Rs.1,00,000 per item need AGM/SGM approval; any item/work above Rs.50,000 needs competitive quotations before finalizing.\nSection 5 Accounts Operation: the bank account is jointly operated by any two office bearers (secretary, treasurer, president, vice-president); the treasurer's signature is mandatory (another office bearer in the treasurer's absence).\nSection 6 Maintenance Fee Collection (Bye-Law Section 43): collected quarterly or yearly in advance, before the due date, by local cheque or electronic transfer; cheque dishonour attracts a bank penalty; delayed payment attracts penal interest of 12% per annum pro-rata.\nSection 7 Financial Statement and Reports: the Secretary and Treasurer prepare accounts and a balance sheet within 3 months of the financial year close; audited and presented at the AGM.\nSection 8 Other Duties: the MC collects maintenance for upkeep, pays municipal taxes/insurance, and prepares/displays the defaulters list.\n\nC. OBLIGATION OF UNIT OWNERS\nSection 9 Assessments (Chapter 5, Section 42): maintenance is due on or before the 10th of the month of the quarter. Arrears of 10 days or more after the due date attract 12% per annum interest from the due date. The Association may recover arrears after notice and may suspend or discontinue common services with up to one week's written notice to a defaulter, may take legal action, and may post defaulters' name/unit/dues on the notice board. On ownership change, amounts paid are not refunded; only advance maintenance/deposits transfer to the new owner if requested; the new owner pays the membership fee and must clear the old owner's arrears and penalties.\nSection 10 Use of Units and Internal Changes (adds to Section 45): no commercial business on the premises. Structural modifications need prior written notice to the MC President; the MC replies within 30 days (no reply within 30 days means no objection); changes harming structural stability are never allowed. No exterior wires/pipes except balconies/ledges for the A/C outdoor unit. Do not obstruct lobbies/stairways/lifts/basement. Balconies must not inconvenience others (no washing/dusting/hanging long items causing nuisance). Open pipelines/sanitary lines must remain accessible (not enclosed). No throwing garbage from windows/balconies; use provided bins. Owners must clear renovation debris (else the Association clears it at the owner's cost plus penalty); written permission is needed for temporary material storage. Passenger lifts must not carry construction or heavy material (penalty plus repair cost); service lifts must be padded for furniture. Non-owner tenants must give an undertaking to abide by the rules. No advertisements/posters without MC authorization; notice-board notices need MC approval and the Secretary/Estate Manager's signature; do not remove notices. No disfiguring or altering common areas or exteriors; balcony covering must follow the Association's prescribed standard. Owners are responsible for their workers, who cannot stay overnight and need temporary ID cards from the Association or security will deny entry.\nSection 11 Rules of Conduct and Occupation: no games such as cricket or tricycle cycling inside the building/lobby/parking. Exercise care with noise, instruments and pets (no free-roaming pets, no nuisance). Do not use maintenance/security staff for personal errands; be polite; complaints in writing to the MC President. No smoking in lifts/common areas/clubhouse/parking. Part-time domestic helpers are allowed only 6:00 AM to 8:00 PM; all helpers/drivers need photo ID cards; they must not sleep or gather in the residential section, play loud music or gamble in common/parking areas, consume or enter after alcohol anywhere in the complex, or run money activities like chit funds/auctions. Residents leaving the station should leave keys with a nearby resident or kin for emergencies. Undocumented matters are interpreted per the Act; the MC decision is final and binding.\nSection 12 Common/Restricted Areas and Facilities: do not obstruct lobbies/stairways/lifts. The clubhouse, gym, common bathrooms and pool are for residents/tenants only; no outsiders except registered live-in guests; the party hall is for an owner's/tenant's invited guests only when booked for a private party. The clubhouse is bookable for a fee for private gatherings via the Manager/register. No fire rituals or political/religious/commercial/outside-organization meetings in the clubhouse. No booking a facility on someone else's behalf. The organizer must clean up brought-in items immediately after a party and is responsible for damage/complaints/misbehaviour; no sticking items on walls. No spitting on walls or in common areas.\nSection 13 Vehicle Movement: resident vehicles must display a valid Association vehicle pass and follow the prescribed entry/exit plan. Visitors record entry/exit at the main gate. Taxis dropping residents leave immediately; unauthorized parking is prohibited. Pick-up taxis/autos enter only after resident approval (MyGate/intercom), must not block passages, and leave within 30 minutes. Speed limit 10 kmph or as displayed.\nSection 14 Vehicle Parking: park only in your allotted space; do not block others. Basement vehicles need a valid pass from the MC office. Guest/visitor vehicles park only in designated visitor parking (or the driveway near the clubhouse if full), per security. Overnight visitor parking needs an approved slot (availability-based); visitor parking beyond 2 consecutive days is not allowed; beyond 2 days it is charged Rs.150/day to the authorizing resident; requests within 48 hours before check-in; first 5 parkings per year per flat get priority. Vendor vehicles use visitor parking for a maximum of 30 minutes, else park outside. 2-wheelers may use any open slot (not visitor or owner 4W slots) first-come, without blocking others. Note: several parking fees were updated by the Visitors Entry and Vehicle Parking Rules effective 01-Jan-2025 (see that document) — prefer the newer figures.\nSection 15 Guests, Vendors and Regular Visitors: all guests enter only after resident approval via MyGate/intercom. Vendors/delivery/workmen enter with resident approval and leave immediately after work; no loitering. Regular visitors (domestic help, drivers, cleaners) get a pass after submitting ID and address proof; entry/exit is notified to residents via MyGate.\nSection 16 Service and Repair Work Inside Flat: get a written MC work permit before noisy work (carpentry, masonry, painting, electrical). No changes to the basic structure or load-bearing walls/beams. No demolishing walls or civil construction without prior written Association permission (especially for water/sanitary pipes). Renovation/repair only 9:00 AM to 6:00 PM; no major noisy work on Sundays/holidays. The Association may inspect anytime.\nSection 17 Fire Safety: do not store belongings in common areas/stairways/parking that obstruct movement. No tampering with fire equipment (extinguishers, hose reels, alarms, hammers, shaft-door keys, PA). Breaking fire glass or a false alarm means paying for damages. No cooking in common areas/parking. Extreme caution with religious open-fire rituals. Learn fire precautions and join drills.\nSection 18 Rental/Lease Agreements and Tenants: share tenant details, police verification and ID proofs with the maintenance office before occupancy. Renting to a group of students/bachelors/working women needs prior MC approval. For students/bachelors/working professionals: maximum 2 persons for a 2BHK and 3 for a 3BHK, prior MC approval, no overnight guests; residents escort guests out before 11:00 PM. For non-family groups, all names must be in the system/agreement with IDs and contacts, with an addendum on any change. Sub-leasing is prohibited. Owners must ensure tenants follow the bye-laws/rules.\nSection 19 Moving-In/Moving-Out: clear all maintenance dues; submit the moving-in/out form; pay a Rs.1000 shifting/admin charge (the first shifting right after builder registration is exempt) plus a Rs.10,000 refundable security deposit before move-out (forfeited to cover damages). Inform one week in advance so security is arranged; the owner is responsible for tenant damage and for restoring common-area/lift damage. Shift goods only after written MC-office approval.\nSection 20 Lifts: use without damaging equipment; do not obstruct. Switch off fans on exit. No writing/graffiti (penalty); do not press buttons with pens/keys/objects. Adults accompany minors. Heavy objects and kids' cycles only via the service lift.\nSection 21 Pets: get BBMP approval/license where applicable before bringing a pet. Keep pets vaccinated and disease-free and share vaccination proof periodically. Prevent harm to others; leash as appropriate and muzzle in open/common areas. If a pet scares/chases/bites, the owner bears all costs. Clean up pet waste immediately (else clean-up charges plus penalty). Pets are not allowed in the terrace, play area, pool, gym, sports room or clubhouse, and not for recreation in the basement. No pet soil on balconies. Prevent excessive barking/growling. Do not leave pets alone in units without an attendant when away.\nSection 22 Gymnasium: open 5:30 to 11:00 AM and 4:00 to 10:00 PM daily. Residents and their accompanied guests only; no outsiders. Under-15s are not allowed. Record details in the clubhouse register. Residents bear the cost of equipment damage. Proper attire; return equipment; wipe benches; brief use to allow others.\nSection 23 Swimming Pool: open 6:00 AM to 8:00 PM daily (maintenance closure other than Sunday, 2:00 to 5:00 PM for about 90 to 120 minutes). Residents and accompanied guests only. Shower before entering; proper attire including swim cap and costume (no regular clothing). Pets strictly prohibited. Minors accompanied by adults. No lifeguard — use at own risk.\nSection 24 Sports Room: open 6:00 AM to 10:00 PM daily. Residents and accompanied guests only. Record details in the register. Care for equipment; minors with adults.\nSection 25 Basketball/Badminton Court/Cricket Net: residents and accompanied guests only. Record sports items in the clubhouse register. Care for equipment; not for drying clothes/cereals. Cricket only with soft balls (no hard balls).\nSection 26 Children's Play Area: play equipment (slides/swings) is only for children about age 8 or lower; adults must not use it. Adults supervise. Cycling/skating only on the driveway in front of the clubhouse; prohibited in basements and no-cycling driveway zones.\nSection 27 Club House: for private celebrations by prior reservation and fee (set by the MC). External vendors may rent it for resident-benefiting promotional/commercial activity with prior permission and fee. Coaches/teachers may use it with prior permission/reservation (free classes allowed; chargeable classes pay the prescribed fee). Private celebration bookings have priority over classes. Maintain care and hygiene; damage is charged to the person who reserved it. No smoking/alcohol; no bulk cooking inside or on the open terrace without MC approval; no stickers/glue on walls.\nSection 28 Gardens, Plants and Landscapes: preserve the flora; no plucking flowers/leaves or uprooting (only small amounts of Tulasi leaves allowed); no trampling or driving over plants (repair borne by the resident); trimming/planting only by the gardener after maintenance-office approval.\nSection 29 Corpus/Reserve Fund (Section 3.10): the corpus fund is non-refundable; no interest is shared to owners; additional funds may be requested (AGM/SGM approved); interest is used to maintain AO assets beyond regular maintenance.\nSection 30 Sinking Fund: used to upkeep the premises; sourced from savings in maintenance charges.\nSection 31 Nuisance: no nuisance or health hazards (pollution, littering, noise). No loud music disturbing others (exceptions with MC approval). No loud chit-chat/laughter near sitting areas such as the senior-citizen park after 9:00 PM. Avoid smoking/loud chatter on balconies near windows. No throwing objects or pouring water/liquid from balconies/windows. No defacing common areas (fines plus repair recovery). Segregate wet and dry waste per BBMP. Do not flush items that clog drains (sanitary pads, diapers, plastic).\n\nD. AMENDMENT\nSection 32 Amendment of the Rule Book: amended in line with the Standard Bye-Law at a duly constituted meeting; the proposal is displayed on the notice board and a soft copy sent to members 15 days prior; it needs at least 75% approval of members present and voting (in person or proxy).\n\nAPPLICABLE RATES AND PENALTIES (Rule Book annexure): Party Hall cleaning charge Rs.3000 (community events free). On-boarding, off-boarding and internal-wing shifting Rs.1000 each; off-boarding also needs a Rs.10,000 refundable security deposit. Wheel-lock for a car parked in the wrong basement location: Rs.500/day unlocking. Overnight basement parking Rs.150/day (per Section 14). Late maintenance payment beyond 10 days from the due date: 12% per annum on the outstanding amount. Cheque dishonour: actual bank charges. Bank-locker document access: Rs.500. Renovation/refurbishment garbage: cleared by the owner.`,\n },\n {\n title: \"Multi-Purpose Party Hall Booking Guidelines\",\n ref: \"Effective 01-Nov-2024\",\n content:\n `MULTI-PURPOSE PARTY HALL BOOKING GUIDELINES, effective 01-Nov-2024.\nBooking: the hall is allotted to flat owners and tenants only (not for friends or relatives), first-come-first-served, via an Association member, the Facility Manager, or MyGate. It may also be allotted for promotional events, but residents get first priority. Two slots: first 8:00 AM to 3:00 PM, second 4:00 PM to 10:00 PM.\nCharges per slot: individual flat owners/tenants Rs.3000; community events/gatherings free; promotional activities Rs.5000 (timing 10:00 AM to 5:00 PM). Charges include electricity, cleaning and BBMP garbage-collection charges. The slot includes decoration/setup time; if the preceding slot is unused, the hirer may seek permission to start decorating earlier or to extend by 1 to 2 hours. Vacate promptly. A refundable security deposit, if collected, is returned within 3 working days after inspection. Payment by cash/UPI at the time of booking to the Association.\nUnavailable dates: 26 January, 15 August, 01 November, Ganesha Chaturthi, and other cultural events run by the cultural team; booking is strictly by availability.\nDecoration: ceiling decorations are not permitted; no nails or cellophane tape on walls; no sticking bills or banners on walls.\nFood and beverage: full-fledged cooking is prohibited; limited veg cooking (e.g. puri, papad) is allowed only at the designated place with protective sheets/cardboard. Liquor is strictly prohibited; smoking and illegal substances are prohibited inside the hall and anywhere in the campus. Food and beverages are served and consumed only within the hall.\nWaste segregation: mandatory at source per BBMP; failure attracts a Rs.1000 penalty.\nGuest car parking: only in the visitor parking near the main gate or in front of the clubhouse; a maximum of 12 guest cars (subject to availability); parking beyond the slot hours or overnight must be informed to security on a chargeable basis.\nCancellation: up to 15 days before the event Rs.1000; up to 1 week before Rs.1500 (unless the hall is re-booked by others); the refund is processed once the date is used by another party.\nGeneral: vacate immediately after the slot and hand over to the facility manager; a maximum of 100 guests including children; no loud music beyond permissible limits or beyond slot timings; band, orchestra and firecrackers are not permitted (a breach is an offense and attracts fines); no fire rituals (Homa/Hawan) inside the hall or common areas; coordinate guest details with the security supervisor or on MyGate; the Association is not responsible for personal belongings or for electricity/DG failures; no events promoting a political agenda, religious bias/conflict or harming social harmony (the AOAOA decision is final); community events need AOAOA approval.\nDamages and missing items: recovered from the hirer at actual cost plus 25% after evaluation, invoiced via a MyGate ID.\nCharges and penalty: a usage-terms violation attracts a Rs.5000 penalty; if it continues, clubhouse access is blocked until further orders from the AOAOA.`,\n },\n {\n title: \"Visitors Entry & Vehicle Parking Rules & Regulations\",\n ref: \"Effective 01-Jan-2025\",\n content:\n `VISITORS ENTRY AND VEHICLE PARKING RULES AND REGULATIONS, effective 01-Jan-2025. (This is the most recent parking document; where it differs from the Rule Book, prefer these figures.)\nResidents pre-approve guest and cab details (with the cab number) in the MyGate app so security can identify and admit them quickly. Taxis and autos may enter up to basement parking for the elderly, the sick, or people carrying luggage, waiting no more than 5 minutes. Delivery personnel make an entry at the security gate, get resident approval, and park their 2-wheeler or 4-wheeler near the gate slot unless authorized to enter with the vehicle.\nGuest parking is allotted by security on a first-come-first-served basis — near-gate slots for short visits and basement for overnight stays (informed to security). Every flat owner/resident can use 1 visitor parking slot for 1 night free of cost each month; it cannot be carried forward and is not transferable. Guest car parking on a chargeable basis is Rs.100 per night; an additional car parking slot is Rs.2000 per month (subject to availability and MC allotment).\nParking violations — parking in a non-designated area or driveway, without gate entry, without a sticker/RFID displayed, or blocking other vehicles — lead to wheel clamping; the wheel-clamp release charge is Rs.200.\nMandatory vehicle entry stickers: all resident vehicles must visibly display an entry sticker for 2-wheelers and an RFID sticker for 4-wheelers to enter. Update vehicles in MyGate/database periodically for sticker/RFID allotment per the assigned parking slots. A 2-wheeler society sticker is Rs.50 and a 4-wheeler RFID is Rs.150 each.\nSpeed limit inside the premises is 10 kmph. No unauthorized parking. Management is not responsible for belongings.`,\n },\n];\n\nconst DOC_TEXT = DOCS.map((d, i) =>\n `\\n===== DOCUMENT ${i + 1}: ${d.title}${\n d.ref ? \" (\" + d.ref + \")\" : \"\"\n } =====\\n${d.content}`\n).join(\"\\n\");\n\nexport const SYSTEM =\n `You are ${NAME}, the assistant for the Aryan Opulence Apartment Owners' Association (AOAOA), a residential complex in Bangalore. Residents ask you about the association's official documents — starting with the registered bye-laws, plus any other documents added below (minutes, circulars, policies, notices, etc.). Answer STRICTLY from the documents provided.\n\nRules for every answer:\n1. Base your answer only on the documents below. Never invent, assume, or add anything that is not written there.\n2. Give a clear, plain-language answer, but do NOT quote or state specific clause, section, article, or point NUMBERS to the resident (never write things like \"Clause 11.3\", \"Section 14\", or \"item 4\"). If helpful you may refer to a source only in general terms (e.g. \"under the association's bye-laws\" or \"per the parking rules\"), never with a number. Reason from the documents internally — just don't expose the citation.\n3. If the resident is asking a yes/no or \"is this within the rules / allowed / correct\" question, START your reply with one line in this EXACT format, then a blank line, then the explanation:\n VERDICT: Within the rules\n VERDICT: Not permitted\n VERDICT: Conditional\n VERDICT: Not covered\n For open or explanatory questions (e.g. \"how are elections held?\"), do NOT add a VERDICT line.\n4. Keep answers concise, plain and practical. Prefer short paragraphs; use a short bullet list only when listing conditions or steps. Paraphrase — quote at most a few words.\n5. If the documents don't cover the point, say so plainly and do NOT guess. Then, instead of simply telling the resident to phone the office, OFFER to send their question to the Managing Committee on their behalf — follow the \"QUESTIONS FOR THE MANAGING COMMITTEE\" steps in your actions (collect the area, plus their name and a REQUIRED email, then log it with log_question) so the committee actually receives it and can reply.\n6. Where a bye-law conflicts with the Karnataka Apartment Ownership Act, 1972, the Act prevails — mention only when relevant, and without citing a clause number.\n7. The Rule Book and the policy documents supplement the bye-laws. Where the bye-laws and the Rule Book differ on a policy matter, the bye-laws take precedence. If two documents give different figures or rules on the same point (for example a parking or booking fee), prefer the one with the most recent effective date, and briefly note the difference so the resident is aware.\n8. You are not a lawyer and must not give legal advice. Present the rules as general guidance, not as a ruling on the committee's conduct: the Managing Committee may apply discretion or act on circumstances, board decisions, or amendments not shown here, so never imply the committee is at fault or has acted wrongly. If a resident is challenging or disputing a committee decision, do NOT adjudicate it — state the general position neutrally and encourage them to raise it respectfully with the Association in writing.\n9. Only answer questions about these documents or living in the complex. Politely decline anything unrelated.\n\nTHE DOCUMENTS:\n${DOC_TEXT}`;",[145],"0fa825f5-b85e-4284-aba6-ebdb88c1e0d3",["D",1784872764062],46,"askaoaoa",[28],"pulls","branches",1,"forks","envVars",{"_166":168,"_169":61},"connections",{"_166":61,"_167":61},"count","unfilledCount",7,"emptyCount",{"_43":153,"_32":28,"_30":31,"_136":-5,"_41":42,"_40":14,"_138":25,"_38":180,"_13":155,"_33":34,"_35":37,"_24":25,"_142":156,"_174":181,"_27":182},{"_43":144,"_32":145,"_30":146,"_136":-5,"_41":42,"_40":147,"_138":25,"_38":177,"_13":149,"_33":150,"_35":151,"_24":25,"_142":-5,"_174":178,"_27":179},{"_43":133,"_32":134,"_30":135,"_136":-5,"_41":42,"_40":137,"_138":25,"_38":173,"_13":140,"_33":34,"_35":141,"_24":25,"_142":-5,"_174":175,"_27":176},["D",1784869322686],"children",[],[134],["D",1784818222591],[],[145],["D",1784872764062],[],[28],["D",1783155855780],["D",1789517443998],{"_98":97,"_106":102},{"_98":97,"_99":100,"_101":102,"_18":55,"_103":104,"_105":25},{"_13":87,"_32":88,"_43":42,"_89":44,"_90":-5,"_91":-5,"_92":-5,"_93":-5,"_94":-5,"_95":45,"_96":97},"ctx",{"_80":-5,"_127":221,"_222":223,"_224":225,"_226":25,"_227":25,"_228":25,"_229":125,"_230":-5,"_231":-7,"_232":-7,"_233":61,"_234":25,"_235":25,"_236":-5,"_237":25,"_238":25,"_239":25,"_240":-5},"ENV",{"_192":193,"_194":195,"_196":88,"_197":198,"_199":200,"_201":202,"_203":204,"_205":206,"_207":208,"_209":210,"_211":212,"_213":214,"_215":216,"_217":218,"_219":220},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","e87eb04e707cf64e7e532c8e8ec395f209e17f15","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]

Diff · v65