AskAOAOA \\u2014 Aryan Opulence Community Assistant

[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_213":214,"_215":216},"routes/_app.x.$handle.$name",{"_100":99,"_34":47,"_109":90,"_28":38,"_13":14,"_110":-5,"_11":111,"_112":113,"_114":115,"_116":117,"_118":119,"_20":-5,"_120":-5,"_121":-5,"_122":27,"_123":124,"_125":25,"_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",{"_45":46,"_34":47,"_40":48,"_49":-5,"_50":27,"_51":52,"_53":52,"_54":55,"_56":-5,"_18":57,"_58":-5,"_59":27,"_60":-5,"_61":-5,"_62":63,"_64":65,"_66":67,"_68":69,"_70":71,"_72":-5,"_73":74,"_75":74,"_76":77,"_78":77,"_79":77,"_80":74,"_81":74,"_82":83,"_84":85,"_86":87,"_88":27},"version",100,"changes",[19],"aiChatInfo","userId",{"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":31},"file",{"_32":33,"_34":29,"_35":36,"_37":39,"_40":41,"_42":14,"_43":44,"_24":27},"previous",{"_32":33,"_34":29,"_35":36,"_37":38},"deleted",true,"deletedHere",false,"path","askaoaoa_data.ts","latestPath","askaoaoa_data_new.ts","fileId","b36952c8-90b2-11f1-b52d-1607ee4eb77e","name","fileType","script","content","","// AskAOAOA — DATA val (Val Town Script val, Unlisted).\n// Exports SYSTEM: the assistant's rules and instructions (persona, verdict format, precedence,\n// no-clause-numbers policy, no-booking guardrail, and the document-library instruction).\n//\n// The association's DOCUMENTS are NOT in this file anymore — they live in a Google Drive folder and\n// are fetched on demand via the get_document tool (see the app vals + the Apps Script ?q=doc endpoint).\n// To add/change a document: edit it in the Drive folder and its row in the Sheet's Documents tab. No code change.\n// The main AskAOAOA vals import SYSTEM from here (set their DATA_URL env var to this val's module URL).\n\n// Community-specific values come from the config val (set CONFIG_URL on the importing vals).\nconst CONFIG = (await import(Deno.env.get(\"CONFIG_URL\"))).CONFIG;\n\nexport const SYSTEM =\n `You are ${CONFIG.name}, the assistant for the ${CONFIG.association}, a residential apartment community. Residents ask you about the association's official documents — starting with the registered bye-laws, plus any other documents in the library (minutes, circulars, policies, notices, etc.). Answer STRICTLY from the documents, which you open on demand with get_document (see below).\n\nRules for every answer:\n1. Base your answer only on the association's documents, which you open with get_document (see THE ASSOCIATION'S 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.\n IMPORTANT EXCEPTION — never add a VERDICT line when the subject of the question is the Managing Committee's own conduct, decision, charge, or action (\"is the committee allowed to...\", \"can the MC charge...\", \"was it legal for them to...\", \"did they follow the rules?\"). A verdict is a judgement on people, and residents may share it out of context. In those cases skip the VERDICT line entirely and follow rule 8 instead: explain the general position neutrally, note that the committee may be acting on decisions or amendments you cannot see, and point them to the committee. The verdict format is for the resident's OWN situation (\"can I park a second car?\", \"am I allowed to keep a pet?\"), not for grading the committee.\n AND, whenever you drop the VERDICT line for this reason, END that reply with the marker [[VERIFY]] on its own line. It is stripped before the resident sees it and replaced with a short note that this is not a ruling. These are exactly the answers a resident is most likely to screenshot, so they must never travel without that note. Use [[VERIFY]] on any answer describing what the committee, the President, or an office-bearer may or must do — even when the answer sounds neutral or favourable to them.\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.\n RECENCY OVERRIDES EVERYTHING ELSE ON A POLICY POINT. The document library is a living record: AGM and EGM minutes, committee resolutions, circulars and revised policies are added over time, and a later adopted decision supersedes an earlier one on the same topic. So when two or more documents speak to the same point (a fee, a timing, a parking or booking rule, an eligibility condition), do NOT simply report the conflict and do NOT default to the oldest or most formal document — work out which is the LATEST adopted position by effective date or meeting date, and give THAT as the answer.\n State the source in plain terms with its date, since that is what makes the answer current and trustworthy: \"as decided at the AGM held on 12 March 2025, the hall charge is now ...\" or \"the parking policy revised in June 2025 supersedes the earlier rule\". Dates and meeting names are ALLOWED and encouraged here — it is only clause, section and article NUMBERS that you must never expose (rule 2).\n Briefly note what changed when it is useful to the resident (\"this replaced the earlier limit of two vehicles\"), so they aren't confused by an older circular they may have seen. If two documents genuinely carry the same date, or you cannot tell which is later, say plainly that the position appears to have changed recently and offer to put the question to the committee (rule 5) rather than guessing.\n If a document is clearly a proposal, draft, agenda item or something \"to be tabled\" rather than a decision that was adopted, do NOT present it as the current rule — say it is under consideration.\n7a. GOVERNANCE QUESTIONS NEED PRECISION, NOT A HEADLINE. Meetings, elections, quorum, voting and office-bearer powers are the topics residents most often act on, and the documents distinguish between bodies that are easy to blur — a General Body Meeting is not a committee meeting, and an Annual General Meeting is not a Special or Extraordinary General Meeting. Before answering, identify WHICH body and WHICH kind of meeting the question is about, and name it that way throughout. Do not compress the answer into a bare \"yes they can\" or \"no they cannot\" when the honest answer is \"this body can do X, that one can do Y\" — lead with the distinction instead. If the documents you opened do not clearly settle which body holds a power, say that plainly and offer to put it to the committee (rule 5); never fill the gap with what such rules usually say elsewhere.\n7b. NEVER STATE A PERSON'S NAME, PHONE NUMBER OR EMAIL FROM MEMORY. Every name, number and address for a committee post or portfolio must come from a get_mc_contacts call made in THIS turn. Do not reuse one you gave earlier in the conversation, do not infer it from a similar-sounding post, and never produce a plausible-looking Indian name or a 10-digit number to fill a gap - a fabricated number may belong to a real stranger who then gets called by residents, and a fabricated office-bearer name is a false statement about a real person. If the tool returns nothing for the post asked about, say plainly that you don't have that post in the committee directory and offer to pass the question on; do not substitute the nearest match. The same rule applies to residents, staff and vendors: names and numbers come from a tool result or they are not said at all.\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.\n YOUR LIBRARY IS NOT THE WHOLE PICTURE. It holds the documents as adopted up to now. The committee may have taken a decision that has not yet been written up, may be acting under an urgency or a practical constraint the documents don't describe, or may be in the middle of formalising a change for a future meeting. Whenever your answer touches on something the committee has done or charged, say so in a natural way — \"the documents I have say X; the committee may have since decided otherwise, so do check with them\" — rather than presenting the document as the final word.\n DO NOT BUILD A CASE AGAINST ANYONE. Decline, warmly and without lecturing, to: draft complaints, legal notices, RTI-style demands or petitions directed at the committee or any office-bearer; compile lists of rules the committee has allegedly broken; assemble a summary of the committee's obligations or failings for use in a dispute; or assess whether someone has grounds to sue, remove, or report an office-bearer. Offer what you legitimately can instead — explain the rule plainly, and offer to send their question or concern to the committee through the proper channel (log_question, log_suggestion or an escalation) so it actually reaches them. The same applies to any request aimed at a specific resident, tenant, staff member or security guard.\n Be even-handed. Never take the resident's side against the committee, and never defend the committee against the resident. If someone is clearly angry, acknowledge the frustration, give them the accurate position, and route them to the people who can actually resolve it.\n9. Only answer questions about these documents or living in the complex. Politely decline anything unrelated.\n10. You provide information only - you cannot make bookings, reservations, or approvals (for example, booking the Multi-Purpose Party Hall). If a resident wants to book or reserve a facility, explain the rules if they ask, but for the booking itself tell them to contact the Managing Committee / association office; never imply a booking can be made through this chat.\n\nTHE ASSOCIATION'S DOCUMENTS:\nYou do NOT have the documents inline. A list of the available documents (title + a short description) is given to you at runtime under \"DOCUMENT LIBRARY\". To answer any question grounded in the association's rules or policies, FIRST call get_document(title) to open the most relevant document(s) from that list, then answer from what it returns. Choose by the descriptions; if unsure, open the closest match, and open more than one if needed. Never answer a rules or policy question from memory without opening the document. (A document you've already opened in this conversation stays available - no need to reopen it.)`;\n\n/* ---------- ACTIONS: the channel behaviour brief ----------\n This was previously duplicated verbatim in the web val and the WhatsApp val (~12k chars each,\n ~10k of it byte-identical). It lives here now so there is ONE copy to edit, and so both app vals\n stay well clear of Val Town's ~80k limit. The app vals call buildActions(\"whatsapp\") / (\"web\").\n Only four lines genuinely differ by channel; everything else below is shared verbatim. */\nexport function buildActions(channel) {\n const wa = channel === \"whatsapp\";\n const pickers = wa\n ? `Pickers: end a message with [[PICK_TOPIC]] to show a tappable list of the areas, or [[PICK_YESNO]] to show Yes/No buttons. When you show a picker, do not also ask them to type. For a date, do NOT use a picker \\u2014 ask the resident to type the date (e.g. 3 July 2025).`\n : `Pickers: 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 const ticketdate = wa\n ? `- If YES: get the ticket ID and a short description. Ask its category ([[PICK_TOPIC]]) and, in a separate message, ask them to type the ticket's creation date (e.g. 3 July 2025).`\n : `- If YES: get the ticket ID and a short description. Ask its category ([[PICK_TOPIC]]) and its creation date ([[PICK_DATE]]).`;\n const attach = wa\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, ${CONFIG.fmsContact}. Then invite them to attach a photo of the issue by ending that message with [[ATTACH:REF]] where REF is that reference number. Screenshots are for escalated issues only.`\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, ${CONFIG.fmsContact}. 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 const contacts = wa\n ? `\\n- ATTACHED CONTACT CARDS: a message beginning [CONTACT CARD SHARED] means the resident attached a contact from their phone instead of typing it. Treat it exactly like a shared recommendation: the name and phone are already there, so do NOT ask for them again. The card rarely says what the person DOES, so if the kind of service isn't obvious from the name or business/role, ask that one short question first (e.g. \"Got it — Ravi Kumar, 98450 12345. What does he do, so I file it correctly?\"). Once you know the category, ask the credit question ending with [[PICK_YESNO]] and then call log_recommendation with the card's details (provider = the name, contact = the phone, area = the address if given, note = the business/role or anything they add). If several cards came in one message, confirm the list, ask the credit question ONCE for all of them, and call log_recommendation separately for each. If the resident shared a contact for some other reason (a plumber for their own complaint, a family member), don't log it — just help with what they actually asked.`\n : \"\";\n return `\n0) RULES & DOCUMENTS. To answer any question about the association's rules or policies, FIRST call get_document to open the most relevant document(s) from the DOCUMENT LIBRARY, then answer from what it returns; never answer a rules question from memory. You give information only - you cannot book, reserve, or approve anything (for example the party hall): explain the rules if asked, but for the booking itself tell the resident to contact the Managing Committee / office, and never imply a booking can be made through this chat.\n\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.\n${pickers}\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 \\u2014 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 \\u2014 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 \\u2014 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${ticketdate}\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${attach}\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.${contacts}\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\n8) FEEDBACK ABOUT THIS ASSISTANT (log_agent_feedback)\nThis is separate from section 1. Section 1 is about the COMMUNITY (a security lapse, an EV-charging idea, an unhappy experience with the building or the committee). This section is about YOU - the assistant: were you useful, accurate, clear; what can't you do that they wish you could; where did you get something wrong.\n- Decide which one it is from what they are commenting on, NOT from the word \"feedback\". \"The gym timings you gave me were wrong\", \"you're quicker than MyGate\", or \"can you also book the hall for me?\" is feedback about the assistant -> log_agent_feedback. \"The gym should open earlier\" is a community suggestion -> log_suggestion. If it is genuinely both, log both and say so briefly.\n- THE COMMENT IS THE POINT, not the score. A star rating on its own tells the committee nothing they can act on. So when a rating arrives with no detail, ask ONE short, specific follow-up - \"what would make it a 5?\" for a high score, \"what did it get wrong, or what were you hoping it could do?\" for a low one - and then log. If their next message answers it, log with that as the comment. If they decline, change the subject, or clearly aren't interested, log it anyway before moving on, with comment \"(no detail given)\" - never drop the rating silently, and never badger them for a reason.\n- Set the kind field honestly: 'bug' when something was wrong or broken, 'feature_request' when they want it to do something new, 'praise' when it simply worked, 'criticism' for a general negative view that isn't a specific fault. Feature requests and bug reports are the most valuable things you can capture here - treat \"can you also do X?\", \"I wish you could...\", \"why can't you...\" and \"that answer was wrong\" as feedback worth logging, not as small talk to brush past.\n- For a bug, capture what they ASKED and what you ANSWERED in the comment, so the committee can reproduce it. If you can see the exchange earlier in this conversation, summarise it yourself rather than making them retype it.\n- Only pass stars if they actually gave a number, and only pass rating if their view is clear - a plain feature request usually has neither. Never invent a score to fill the field.\n- Their flat is recorded so the committee can follow up. If they ask to stay anonymous, set anonymous true and confirm you've kept it anonymous.\n- Thank them briefly and sincerely. Never argue with criticism, never defend yourself at length, and never promise a fix or a new feature - say the committee will see it.\n- Never ask for feedback in the middle of a complaint, escalation or dues query, and never ask for it twice in one conversation.\n\nAnswer ordinary questions from the documents as usual; only log a question when you genuinely cannot answer it.`;\n}\n\n/* ---------- TOOLS: the resident-facing tool schemas ----------\n Previously duplicated in both app vals (~10.3k each, 114 of 115 lines byte-identical). One copy\n here means one place to edit, and it keeps both app vals clear of Val Town's ~80k limit.\n The copilot's own small tool list stays in the app vals - it is genuinely different per channel. */\nexport function buildTools(TOPICS) {\n return [\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: {\n type: \"string\",\n description: \"Optional: the resident's name.\",\n },\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: {\n type: \"string\",\n description: \"Optional: the resident's name.\",\n },\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:\n \"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. The record may include extra fields the committee added as columns on the Residents tab; treat them the same way \\u2014 use them if they clearly answer the question, ignore them if their meaning is unclear.\",\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: \"log_agent_feedback\",\n description:\n \"Record what the resident thinks of THIS ASSISTANT itself — whether it was useful, accurate, easy to use, or what it's missing. This is NOT for suggestions about the community, the building, or the committee's work: those go to log_suggestion. Use this only when the resident is commenting on the assistant/bot.\",\n input_schema: {\n type: \"object\",\n properties: {\n kind: {\n type: \"string\",\n enum: [\"bug\", \"feature_request\", \"praise\", \"criticism\"],\n description:\n \"'bug' = something the assistant got wrong or that isn't working. 'feature_request' = something they wish it could do. 'praise' = it worked well. 'criticism' = a general negative view that isn't a specific bug.\",\n },\n comment: {\n type: \"string\",\n description:\n \"REQUIRED. What they said, in their own words \\u2014 this is what the committee actually acts on. For a bug, include what they asked and what the assistant answered, so it can be reproduced. For a feature request, describe what they want to be able to do. If they gave a rating but genuinely won't elaborate, write '(no detail given)'.\",\n },\n stars: {\n type: \"integer\",\n description:\n \"1-5 if the resident gave a star rating. Omit entirely if they didn't \\u2014 never invent one. A feature request usually has no rating.\",\n },\n rating: {\n type: \"string\",\n enum: [\"up\", \"down\", \"mixed\"],\n description:\n \"Coarse sentiment, only if it is clear and no star rating was given: 'up' positive, 'down' negative, 'mixed' both. Omit for a neutral feature request.\",\n },\n anonymous: {\n type: \"boolean\",\n description:\n \"True if the resident asked to keep it anonymous. Default false \\u2014 their flat is recorded so the committee can follow up.\",\n },\n },\n required: [\"kind\", \"comment\"],\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. Rows may also carry an \"extra\" object holding columns the committee has added to the sheet themselves (for example a Flat column): use those values naturally when they answer what was asked, and never guess what an unfamiliar column means \\u2014 if its meaning is not obvious from its name, ignore it rather than misdescribe it.',\n input_schema: { type: \"object\", properties: {}, required: [] },\n },\n {\n name: \"get_document\",\n description:\n \"Open one of the association's documents from the DOCUMENT LIBRARY and get its full text, so you can answer a rules or policy question. Pass the exact Title shown in the library. Call this before answering anything grounded in the bye-laws, rule book, parking, party hall, or any listed document.\",\n input_schema: {\n type: \"object\",\n properties: {\n title: {\n type: \"string\",\n description:\n \"The exact document Title from the DOCUMENT LIBRARY list.\",\n },\n },\n required: [\"title\"],\n },\n },\n ];\n}","createdAt",["D",1785923320880],"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",{"_100":99,"_108":104},"org",{"_100":99,"_101":102,"_103":104,"_18":57,"_105":106,"_107":27},"branch",{"_13":89,"_34":90,"_45":44,"_91":46,"_92":-5,"_93":-5,"_94":-5,"_95":-5,"_96":-5,"_97":47,"_98":99},"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",{"_45":46,"_34":47,"_40":208,"_49":-5,"_50":27,"_51":52,"_53":52,"_54":55,"_56":-5,"_18":57,"_58":-5,"_59":27,"_60":-5,"_61":-5,"_62":63,"_64":65,"_66":67,"_68":69,"_70":209,"_72":-5,"_73":74,"_75":74,"_76":77,"_78":77,"_79":77,"_80":74,"_81":74,"_82":210,"_84":211,"_86":212,"_88":27},"tree",[187,188,189,190,191],"files",[187,188,189,190,191],"counts",{"_175":63,"_176":177,"_178":63,"_179":180,"_181":182},"contents",[130,131,132,133,134],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_45":167,"_34":168,"_32":169,"_138":-5,"_43":44,"_42":170,"_140":27,"_40":171,"_13":172,"_35":36,"_37":173,"_24":27,"_145":-5,"_28":174},{"_45":158,"_34":159,"_32":160,"_138":-5,"_43":44,"_42":161,"_140":27,"_40":162,"_13":163,"_35":143,"_37":164,"_24":27,"_145":165,"_28":166},{"_45":154,"_34":29,"_32":33,"_138":-5,"_43":44,"_42":14,"_140":27,"_40":155,"_13":156,"_35":36,"_37":39,"_24":27,"_145":-5,"_28":157},{"_45":147,"_34":148,"_32":149,"_138":-5,"_43":44,"_42":150,"_140":27,"_40":151,"_13":152,"_35":36,"_37":39,"_24":27,"_145":-5,"_28":153},{"_45":135,"_34":136,"_32":137,"_138":-5,"_43":44,"_42":139,"_140":27,"_40":141,"_13":142,"_35":143,"_37":144,"_24":27,"_145":-5,"_28":146},"4cf8acfe-788d-4ad5-9ebc-d1cf4ff9aada","askaoaoa_page.ts","9af845d6-871c-11f1-bcc1-1607ee4eb77e","parentId",66,"latest",["D",1784873879474],5,"http","// 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\\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",[136],"7f6e601e-4877-492b-9f75-617090e22e6b","askaoaoa_data_stale.ts","98ea1bc8-79fe-11f1-a4d2-1607ee4eb77e",97,["D",1785923255425],16,[148],"ead3aa2a-721b-4b48-9a4b-d0e5c3547965",["D",1785923320880],2,[29],"68635afb-b096-4881-b92c-2f4eb78e57e4","askaoaoa.ts","55270802-7787-11f1-b236-1607ee4eb77e",96,["D",1785908299316],58,"// 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;\nconst FEEDBACK_WIDGET = `\n\n\n\n\n

How is this assistant working for you?

Goes to the Managing Committee only. It helps them fix what is broken and decide what to add next.

\n\n Rating\n

\n\n What is this about?\n

\n\n In your words\n \n\n \n \n \n Send without my flat number\n \n\n

\n \n \n

\n\n\n`;\n\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 // brand the page from CONFIG (case-sensitive; internal ids use lowercase 'aoaoa' and are untouched)\n const B = CONFIG.brand || {};\n PAGE_CACHE = mod.PAGE\n .split(\"AskAOAOA\").join(CONFIG.name)\n .split(\"Aryan Opulence\").join(CONFIG.estateShort)\n .split(\"--ink:#16302B\").join(\"--ink:#\" + (B.ink || \"16302B\"))\n .split(\"--ink-2:#0F231F\").join(\"--ink-2:#\" + (B.ink2 || \"0F231F\"))\n .split(\"--brass:#B5852C\").join(\"--brass:#\" + (B.accent || \"B5852C\"))\n .split(\"--sage:#5E7168\").join(\"--sage:#\" + (B.sage || \"5E7168\"));\n try {\n const _t = await getTopics();\n PAGE_CACHE = PAGE_CACHE.replace(\n /const TOPICS = \\[[\\s\\S]*?\\];/,\n \"const TOPICS = \" + JSON.stringify(_t) + \";\",\n );\n } catch (e) {}\n // Feedback widget is injected here rather than living in the page val, so the frontend HTML never\n // has to change. It reads the access code and last exchange off the /api traffic it wraps, so it\n // needs no knowledge of the page's own markup.\n if (PAGE_CACHE.indexOf(\"aoafb-open\") < 0) {\n const _i = PAGE_CACHE.toLowerCase().lastIndexOf(\"\");\n PAGE_CACHE = (_i >= 0)\n ? (PAGE_CACHE.slice(0, _i) + FEEDBACK_WIDGET + PAGE_CACHE.slice(_i))\n : (PAGE_CACHE + FEEDBACK_WIDGET);\n }\n return PAGE_CACHE;\n}\n\n// ---- per-community config (the config val). Set CONFIG_URL to its ES-module URL. ----\nconst CONFIG_URL = Deno.env.get(\"CONFIG_URL\");\nif (!CONFIG_URL) throw new Error(\"CONFIG_URL not set\");\nconst _cfg = await import(CONFIG_URL);\nconst CONFIG = _cfg.CONFIG;\nconst NAME = CONFIG.name;\nconst TOPICS = CONFIG.topics;\nconst isValidFlat = (raw) => _cfg.isValidFlat(raw, CONFIG);\nconst normalizeFlat = (raw) => _cfg.normalizeFlat(raw, CONFIG);\n\nlet MANIFEST_CACHE = {}, MANIFEST_TS = {};\nasync function getManifest(mc) {\n const key = mc ? \"mc\" : \"all\";\n const now = Date.now();\n if (MANIFEST_CACHE[key] != null && (now - (MANIFEST_TS[key] || 0)) < 300000) {\n return MANIFEST_CACHE[key];\n }\n let txt = \"\";\n try {\n const r = await sheetGet(\"q=docs\" + (mc ? \"&scope=mc\" : \"\"));\n if (r && r.ok && Array.isArray(r.docs) && r.docs.length) {\n txt =\n \"DOCUMENT LIBRARY (open the relevant one with get_document before answering):\\n\" +\n r.docs.map(function (x) {\n return \"- \" + x.title + (x.description ? \": \" + x.description : \"\") +\n (x.audience === \"mc\" ? \" [committee-only]\" : \"\");\n }).join(\"\\n\");\n }\n } catch (e) {}\n MANIFEST_CACHE[key] = txt;\n MANIFEST_TS[key] = now;\n return txt;\n}\n\nlet TOPICS_CACHE = null, TOPICS_TS = 0;\nasync function getTopics() {\n const now = Date.now();\n if (TOPICS_CACHE !== null && (now - TOPICS_TS) < 300000) return TOPICS_CACHE;\n let list = null;\n try {\n const r = await sheetGet(\"q=topics\");\n if (r && r.ok && Array.isArray(r.topics) && r.topics.length) {\n list = r.topics;\n }\n } catch (e) {}\n TOPICS_CACHE = (list && list.length) ? list : CONFIG.topics; // fallback to config if the sheet has none\n TOPICS_TS = now;\n return TOPICS_CACHE;\n}\n\n// Tool schemas now live in the data val (one shared copy). Fetched and cached like ACTIONS.\nlet TOOLS_CACHE = null;\nasync function getTools(TOPICS) {\n if (TOOLS_CACHE) return TOOLS_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 if (typeof mod.buildTools !== \"function\") {\n console.log(\n \"FATAL: data val at DATA_URL has no buildTools export - update DATA_URL to the latest data val module URL.\",\n );\n throw new Error(\n \"Data val is out of date: no buildTools export. Update DATA_URL.\",\n );\n }\n TOOLS_CACHE = mod.buildTools(TOPICS);\n return TOOLS_CACHE;\n}\n\n// ACTIONS now lives in the data val (one shared copy). Fetched and cached by getActions().\nlet ACTIONS_CACHE = null;\nasync function getActions() {\n if (ACTIONS_CACHE != null) return ACTIONS_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 if (typeof mod.buildActions !== \"function\") {\n // Deterministic misconfiguration, not a transient blip: the data val loaded but is an OLD copy\n // without buildActions (usually DATA_URL pinned to an earlier version). Fail loudly - silently\n // serving an empty ACTIONS would strip every action instruction while still looking healthy.\n console.log(\n \"FATAL: data val at DATA_URL has no buildActions export - update DATA_URL to the latest data val module URL.\",\n );\n throw new Error(\n \"Data val is out of date: no buildActions export. Update DATA_URL.\",\n );\n }\n ACTIONS_CACHE = mod.buildActions(\"web\");\n // Fingerprint the loaded prompt so you can tell from the logs whether the data val you just\n // saved is actually the one being served (a pinned DATA_URL fails silently otherwise).\n const _sys = String(mod.SYSTEM || \"\");\n console.log(\n \"prompt loaded: actions=\" + ACTIONS_CACHE.length + \" chars, system=\" +\n _sys.length +\n \", grounding_rule=\" + (_sys.indexOf(\"NEVER STATE A PERSON\") >= 0\n ? \"yes\"\n : \"NO - DATA VAL IS STALE\"),\n );\n return ACTIONS_CACHE;\n}\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 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 const ctl = new AbortController();\n const timer = setTimeout(() => ctl.abort(), 15000); // writes get longer than reads, but not forever\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 signal: ctl.signal,\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 if (e && e.name === \"AbortError\") {\n console.log(\"postSheet timed out: \" + (payload && payload.type));\n }\n return { ok: false, note: \"Could not reach the logging service.\" };\n } finally {\n clearTimeout(timer);\n }\n}\n\nlet STATUS_CACHE = { t: 0, v: \"\" };\n/* Every Apps Script call is time-boxed. Without this, one slow doGet blocks the whole answer: a\n 45-second preflight was observed in production, which is past the platform request timeout, so the\n isolate was killed and the resident got complete silence. A degraded answer beats no answer. */\nasync function sheetGet(query, timeoutMs) {\n if (!WEBHOOK) {\n return {\n ok: false,\n note: \"Lookups are not set up yet (no SHEET_WEBHOOK_URL).\",\n };\n }\n const ctl = new AbortController();\n const timer = setTimeout(() => ctl.abort(), timeoutMs || 8000);\n try {\n const url = WEBHOOK + \"?\" + query +\n (SHEET_SECRET ? \"&secret=\" + encodeURIComponent(SHEET_SECRET) : \"\");\n const r = await fetch(url, { redirect: \"follow\", signal: ctl.signal });\n return await r.json();\n } catch (e) {\n if (e && e.name === \"AbortError\") {\n console.log(\"sheetGet timed out: \" + String(query).slice(0, 60));\n }\n return { ok: false, note: \"Could not reach the lookup service.\" };\n } finally {\n clearTimeout(timer);\n }\n}\n/* One Apps Script call instead of three. Val Town gives us a COLD isolate on essentially every\n message (the \"prompt loaded\" line appears on each request), so the in-process caches below almost\n never survive to be reused - which made the old three-call preflight cost three cold Apps Script\n executions per resident message. If the endpoint is missing (Apps Script not yet redeployed) this\n falls back to the individual calls, so it is safe to deploy the vals first. */\nasync function preflight(mc) {\n const d = await sheetGet(\"q=preflight\" + (mc ? \"&scope=mc\" : \"\"), 8000);\n if (!d || !d.ok || !Array.isArray(d.topics)) return false;\n const now = Date.now();\n let v = \"\";\n if (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 STATUS_CACHE = { t: now, v: v };\n if (d.topics.length) {\n TOPICS_CACHE = d.topics;\n TOPICS_TS = now;\n }\n const key = mc ? \"mc\" : \"all\";\n let txt = \"\";\n if (Array.isArray(d.docs) && d.docs.length) {\n txt =\n \"DOCUMENT LIBRARY (open the relevant one with get_document before answering):\\n\" +\n d.docs.map(function (x) {\n return \"- \" + x.title + (x.description ? \": \" + x.description : \"\") +\n (x.audience === \"mc\" ? \" [committee-only]\" : \"\");\n }).join(\"\\n\");\n }\n MANIFEST_CACHE[key] = txt;\n MANIFEST_TS[key] = now;\n return true;\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 = \"You are the \" + NAME +\n \" Committee Copilot for the Managing Committee (MC) of \" +\n CONFIG.estateShort + \" Apartments, a \" + CONFIG.unitCount +\n \"-flat community. You are given recent community data as JSON (complaints with status, suggestions, questions, escalations, site-status posts, neighbour recommendations, and agentFeedback \\u2014 residents' ratings of the assistant itself, rated up/down/mixed with their comment and channel), newest first. Help the committee: summarise and count, spot recurring themes, list open/pending items and prioritise them, report how residents rate the assistant itself (satisfaction trend, common gaps) when asked, 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 can also open any association document from the DOCUMENT LIBRARY with the get_document tool \\u2014 including committee-only data such as boom-barrier/vehicle logs or security attendance \\u2014 to analyze it: summarise, count, find patterns or outliers (for example, which security staff were least punctual last quarter), and cite exact figures. For a rules question you MAY quote exact clause or section numbers to the committee (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 manifest = await getManifest(true); // committee scope: includes committee-only documents\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: \"REFERENCE \\u2014 the association's rules/instructions:\\n\\n\" + sys,\n });\n }\n if (manifest) system.push({ type: \"text\", text: manifest });\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 tools = [{\n name: \"get_document\",\n description:\n \"Open any association document from the DOCUMENT LIBRARY \\u2014 including committee-only ones (e.g. boom-barrier/vehicle logs, security attendance) \\u2014 and get its full text or data to analyze. Pass the exact Title from the library.\",\n input_schema: {\n type: \"object\",\n properties: {\n title: {\n type: \"string\",\n description: \"The exact Title from the DOCUMENT LIBRARY.\",\n },\n },\n required: [\"title\"],\n },\n }];\n let 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 for (let step = 0; step < 6; step++) {\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: CONFIG.models.copilot,\n max_tokens: 2000,\n temperature: 0,\n system: system,\n tools: tools,\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 if (cd.stop_reason === \"tool_use\") {\n const results = [];\n for (const b of (cd.content || [])) {\n if (b.type === \"tool_use\" && b.name === \"get_document\") {\n const res = await sheetGet(\n \"q=doc&scope=mc&title=\" +\n encodeURIComponent((b.input && b.input.title) || \"\"),\n );\n results.push({\n type: \"tool_result\",\n tool_use_id: b.id,\n content: JSON.stringify(res).slice(0, 120000),\n });\n } else if (b.type === \"tool_use\") {\n results.push({\n type: \"tool_result\",\n tool_use_id: b.id,\n content: \"(unavailable)\",\n });\n }\n }\n msgs.push({ role: \"assistant\", content: cd.content });\n msgs.push({ role: \"user\", content: results });\n continue;\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 }\n return \"That needed too many steps \\u2014 please narrow the question.\";\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 CONFIG.fmsContact + \".\",\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 === \"log_agent_feedback\") {\n return await postSheet({\n type: \"agent_feedback\",\n kind: input.kind || \"\",\n stars: (input.stars >= 1 && input.stars <= 5) ? input.stars : \"\",\n rating: input.rating || \"\",\n comment: input.comment || \"\",\n flat: input.anonymous ? \"\" : (flat || \"\"),\n channel: \"Web\",\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 if (name === \"get_document\") {\n return await sheetGet(\n \"q=doc&title=\" + encodeURIComponent(input.title || \"\"),\n );\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: CONFIG.models.resident,\n max_tokens: 1000,\n temperature: 0,\n system: systemBlocks,\n tools: await getTools(await getTopics()),\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 // Feedback from the injected page widget (no AI call - a direct write, like /upload).\n if (req.method === \"POST\" && url.pathname === \"/feedback\") {\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({\n ok: false,\n note: \"Please enter your access code in the chat first.\",\n }, 401);\n }\n const kind = String((b && b.kind) || \"\").toLowerCase();\n if ([\"bug\", \"feature_request\", \"praise\", \"criticism\"].indexOf(kind) < 0) {\n return json({ ok: false, note: \"Pick what this is about.\" }, 400);\n }\n let comment = String((b && b.comment) || \"\").trim().slice(0, 2000);\n if (!comment) {\n return json({\n ok: false,\n note: \"Add a line or two so the committee knows what to do.\",\n }, 400);\n }\n // Attach the exchange the resident agreed to share, so a bug can be reproduced.\n const cx = b && b.context;\n if (cx && (cx.question || cx.answer)) {\n comment += \"\\n\\n--- resident's last exchange ---\\nAsked: \" +\n String(cx.question || \"\").slice(0, 800) +\n \"\\nAnswered: \" + String(cx.answer || \"\").slice(0, 1200);\n }\n const st = parseInt(b && b.stars, 10);\n // Derive the flat server-side from the access code, exactly as the chat path does - never trust\n // a client-supplied flat.\n const fbFlat = (MODE === \"flat\" && !(b && b.anonymous))\n ? String((b && b.code) || \"\").trim().toUpperCase()\n : \"\";\n const res = await postSheet({\n type: \"agent_feedback\",\n kind: kind,\n stars: (st >= 1 && st <= 5) ? st : \"\",\n comment: comment,\n flat: fbFlat,\n channel: \"Web\",\n });\n return json(\n res && res.ok\n ? { ok: true }\n : { ok: false, note: \"That did not send. Please try again.\" },\n (res && res.ok) ? 200 : 500,\n );\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 // Was the resident's latest question about what the committee may or must do? Used below as the\n // deterministic trigger for the verification note.\n let _askedConduct = false;\n for (let i = messages.length - 1; i >= 0; i--) {\n if (messages[i].role === \"user\") {\n _askedConduct = isCommitteeConductQuestion(messages[i].content);\n break;\n }\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 // These three are independent; running them in series added seconds to every answer.\n const [, actionsText] = await Promise.all([preflight(false), getActions()]);\n // these now read the caches preflight just filled; they only hit the network if it failed\n const [siteStatus, manifest] = await Promise.all([\n getStatus(),\n getManifest(),\n ]);\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 + actionsText + (manifest ? \"\\n\\n\" + manifest : \"\"),\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 // Verdicts, and answers about committee conduct (marked [[VERIFY]]), are what residents\n // screenshot - neither travels without the \"not a ruling\" note.\n const _vf = /\\[\\[VERIFY\\]\\]/i.test(b.text);\n if (_vf) b.text = b.text.replace(/\\[\\[VERIFY\\]\\]/gi, \"\").trim();\n if (\n CONFIG.verifyNote &&\n (_vf || _askedConduct || /^\\s*VERDICT:\\s*\\S/im.test(b.text))\n ) b.text = b.text.trim() + \"\\n\\n\" + CONFIG.verifyNote;\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 NAME + \" \\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\n/* ---------- committee-conduct detector ----------\n Deterministic backstop for the verification note: if the RESIDENT's question is about what the\n committee or an office-bearer may, must, or cannot do, the note is attached regardless of whether\n the model emitted [[VERIFY]]. A safety footer must not depend on model compliance. */\nconst COMMITTEE_RX =\n /\\b(committee|managing committee|\\bmc\\b|office[- ]?bearer|president|secretary|treasurer|association)\\b/i;\nconst CONDUCT_RX =\n /\\b(can|cannot|can't|could|allowed|permitted|entitled|empower\\w*|authoris\\w*|authoriz\\w*|legal|illegal|valid|right|rights|power|powers|must|should|supposed to|oblig\\w*|breach\\w*|violat\\w*|wrong\\w*|unfair\\w*|arbitrar\\w*|overcharg\\w*|misus\\w*|answerable|accountab\\w*|unilateral\\w*|whim|sudden\\w*)\\b/i;\nfunction isCommitteeConductQuestion(t) {\n const s = String(t || \"\");\n if (!s.trim()) return false;\n return COMMITTEE_RX.test(s) && CONDUCT_RX.test(s);\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}","askaoaoa",[159],"70bcfb84-8214-4b4f-8026-1e17c0dfce8d","askaoaoa-config.ts","e630533a-8a88-11f1-95ce-1607ee4eb77e",88,["D",1785860463905],8,"// AskAOAOA — CONFIG val (Val Town Script val, Unlisted). ONE per community.\n//\n// This is the ONLY file that changes from one apartment to the next. The knowledge val\n// (rules) and the two app vals (web + WhatsApp) read everything community-specific from here,\n// so a new community = a new copy of this file + its own Sheet / Drive folder / WhatsApp number.\n//\n// The app vals import this via their CONFIG_URL env var (set it to this val's ES-module URL,\n// e.g. https://esm.town/v//askaoaoa_config).\n//\n// To rename the assistant: change `name` below (and regenerate the page val for the web branding).\n\nexport const CONFIG = {\n id: \"aryan-opulence\", // slug; used only for internal namespacing\n name: \"AskAOAOA\", // assistant display name\n association: \"Aryan Opulence Apartment Owners' Association\",\n estateShort: \"Aryan Opulence\", // short name used in messages\n unitCount: 189,\n languages: [\"English\", \"Hindi\", \"Kannada\"], // offered languages, in order\n fmsContact: \"Sandeep on +91 91108 02505\", // FMS (facility) manager, quoted to residents on escalations\n disclaimer:\n \"_I'm an AI assistant and can occasionally be wrong \\u2014 please verify anything important with the Managing Committee._\",\n // Appended to any answer that carries a VERDICT line, so a screenshot of it never travels\n // without context. Keep it short: it rides along on real answers.\n verifyNote:\n \"_This is general information from the association's documents, not a ruling. The committee may have since decided otherwise \\u2014 please check with them._\",\n credit: \"Built by Shyam A Nair (602-C), as a community volunteer effort.\", // shown in the web + WhatsApp About\n\n // Flat scheme — replaces the old hardcoded isValidFlat(). Accepts \"602-C\" or \"C-602\":\n // the last two digits are the flat, the leading digit(s) are the floor \"series\".\n flats: {\n blocks: [\"a\", \"b\", \"c\", \"d\"],\n limits: {\n a: { maxSeries: 11, maxFlat: 6 },\n b: { maxSeries: 11, maxFlat: 4 },\n c: { maxSeries: 10, maxFlat: 4 },\n d: { maxSeries: 10, maxFlat: 4 },\n },\n },\n\n // FALLBACK topic list only. Topics now derive from the MC Contacts Portfolio rows (+ \"Others\")\n // via the ?q=topics endpoint; this list is used only if that returns nothing.\n 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\n // Web page brand colours (hex, no \"#\"): header/primary (ink), gradient end (ink2),\n // accent/gold (accent), and muted green (sage). Edit these to re-theme the web app.\n brand: { ink: \"16302B\", ink2: \"0F231F\", accent: \"B5852C\", sage: \"5E7168\" },\n\n // LLM routing (mode-based): a cheaper/faster model for the high-volume resident agent,\n // a stronger model for the committee copilot. Flip either back to the same value to undo.\n models: { resident: \"claude-haiku-4-5-20251001\", copilot: \"claude-sonnet-5\" },\n};\n\n// ---- Generic flat validation, driven by CONFIG.flats (no per-community code) ----\nfunction flatRegexes(cfg) {\n const cls = ((cfg.flats && cfg.flats.blocks) || []).join(\"\");\n return [\n new RegExp(\"^(\\\\d{3,4})-?([\" + cls + \"])$\"),\n new RegExp(\"^([\" + cls + \"])-?(\\\\d{3,4})$\"),\n ];\n}\nfunction parseFlat(raw, cfg) {\n const s = String(raw || \"\").trim().toLowerCase().replace(/\\s+/g, \"\");\n const [re1, re2] = flatRegexes(cfg);\n const m = s.match(re1) || s.match(re2);\n if (!m) return null;\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 return {\n digits,\n block,\n flat: parseInt(digits.slice(-2), 10),\n series: parseInt(digits.slice(0, -2), 10),\n };\n}\nexport function isValidFlat(raw, cfg) {\n cfg = cfg || CONFIG;\n const p = parseFlat(raw, cfg);\n if (!p) return false;\n const lim = (cfg.flats.limits && cfg.flats.limits[p.block]) || {};\n const maxSeries = lim.maxSeries || 99, maxFlat = lim.maxFlat || 99;\n return p.series >= 1 && p.series <= maxSeries && p.flat >= 1 &&\n p.flat <= maxFlat;\n}\nexport function normalizeFlat(raw, cfg) {\n cfg = cfg || CONFIG;\n const p = parseFlat(raw, cfg);\n if (!p) return String(raw || \"\").trim().toUpperCase();\n return (p.digits + \"-\" + p.block).toUpperCase();\n}",[168],"pulls","branches",1,"forks","envVars",{"_183":185,"_186":63},"connections",{"_183":63,"_184":63},"count","unfilledCount",7,"emptyCount",{"_45":167,"_34":168,"_32":169,"_138":-5,"_43":44,"_42":170,"_140":27,"_40":205,"_13":172,"_35":36,"_37":173,"_24":27,"_145":-5,"_193":206,"_28":207},{"_45":158,"_34":159,"_32":160,"_138":-5,"_43":44,"_42":161,"_140":27,"_40":202,"_13":163,"_35":143,"_37":164,"_24":27,"_145":165,"_193":203,"_28":204},{"_45":154,"_34":29,"_32":33,"_138":-5,"_43":44,"_42":14,"_140":27,"_40":199,"_13":156,"_35":36,"_37":39,"_24":27,"_145":-5,"_193":200,"_28":201},{"_45":147,"_34":148,"_32":149,"_138":-5,"_43":44,"_42":150,"_140":27,"_40":196,"_13":152,"_35":36,"_37":39,"_24":27,"_145":-5,"_193":197,"_28":198},{"_45":135,"_34":136,"_32":137,"_138":-5,"_43":44,"_42":139,"_140":27,"_40":192,"_13":142,"_35":143,"_37":144,"_24":27,"_145":-5,"_193":194,"_28":195},["D",1784873879474],"children",[],[136],["D",1785923255425],[],[148],["D",1785923320880],[],[29],["D",1785908299316],[],[159],["D",1785860463905],[],[168],["D",1783155855780],["D",1789517443998],{"_100":99,"_108":104},{"_100":99,"_101":102,"_103":104,"_18":57,"_105":106,"_107":27},{"_13":89,"_34":90,"_45":44,"_91":46,"_92":-5,"_93":-5,"_94":-5,"_95":-5,"_96":-5,"_97":47,"_98":99},"ctx",{"_82":-5,"_127":246,"_247":248,"_249":250,"_251":27,"_252":27,"_253":27,"_254":25,"_255":-5,"_256":-7,"_257":-7,"_258":63,"_259":27,"_260":27,"_261":-5,"_262":27,"_263":27,"_264":27,"_265":-5},"ENV",{"_217":218,"_219":220,"_221":90,"_222":223,"_224":225,"_226":227,"_228":229,"_230":231,"_232":233,"_234":235,"_236":237,"_238":239,"_240":241,"_242":243,"_244":245},"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 · v100