FIKI / KNOWLEDGE BASE
Browse the approved public material FIKI uses to answer questions about TOHS rules, tools, and housing-post formats.
Extracted only the explanatory/help copy from the legacy Live Filter page shell; the actual filter controls, results feed, and data sync are application-layer behavior built against the public-safe views, not knowledge content.
Read article →Combines the mission/identity copy with a durable history section, removing dated statistics (post-review counts, download counts, country-engagement numbers) that need to stay current rather than hard-coded. Rewritten to drop overstated "Market Governance"/"Legal Void Defense" framing from the old dashboard-style layout, in favour of plain description. A separate case-study page about the 2026 migration/redesign is a distinct future content item, not drafted here.
Read article →Extracts only the stable explanatory copy from the legacy dashboard shell. Charts, live status text (e.g., "UPDATED JAN 2026", "PRICING IN DECLINE"), and calculations are application-layer behavior built against the real analytics pipeline, not knowledge content -- these should never be hard-coded again. The realtor-recommendation block from the legacy page is deliberately not carried into this content entry: whether any third-party/realtor recommendation belongs anywhere in the public experience is explicitly deferred until the KB-005 supporter-policy module is designed (unresolved open question, unchanged from original triage).
Read article →Fills a real gap: FIKI had no fallback answer for "I emailed and haven't heard back" style questions. Keeps the guidance generic to "moderators" rather than naming any specific individual, since team composition changes.
Read article →Rewrites the legacy "Chronicle" naming and "real-time feed" framing to match the actual public-safe published-view data model (not a live mirror of raw Facebook posts). Removes the unverified "140,000+ members" claim until a real, current figure is available (see the TOHS Community Size entry).
Read article →Confusion between "permission to sublet generally" and "permission for this specific subtenant" is a recurring real-world problem -- LTB order records show unauthorized-occupant cases where this distinction determined financial liability. See also the Sublet Rules and Template Guide (KB-022) for the fuller version of this permission point and the deferred LTB-outcome-statistics feature that will eventually back this claim with real aggregate numbers.
Read article →Extracted from the legacy Posting Formats template; kept as the plain-language checklist version rather than the raw copy-paste template (the template itself remains a tool-page feature, not knowledge content).
Read article →Extracted from the legacy Posting Formats page and the posts_offering review_rules moderation logic (photo requirements, den labeling, basement-window rule, per-room pricing, split-post rule).
Read article →Corrects the previous public claim that these caps were based on CMHC/StatsCan data -- they were not. The real derivation is City of Toronto affordable-housing maximums plus internal community calibration, as confirmed directly by the TOHS founder. This content is now a section within the Posting Rules page (not a standalone page); /cap should redirect here.
Read article →Tenants often don't know rent receipts are a legal entitlement (not a landlord courtesy), and may need a properly worded request if a landlord is unresponsive or refuses.
Read article →Off-lease roommate situations sit outside the RTA's tenant-landlord framework, so people often mistakenly assume LTB processes apply when they don't -- this FAQ exists to set accurate expectations and reduce disputes.
Read article →Extracted the legal/context sections into this atomic entry; removed stale community-size claims from the old copy. Google Drive remains the deliberate single source of truth for the template (both Word-doc download and "make a copy" editable option) -- this was evaluated and confirmed, not a gap to fix.
Read article →Fills a real gap: FIKI had no knowledge of this thread and could not mention it when someone described a short-duration or temporary rental need. This is a THZ-specific community mechanic, not a formal posting-rules category.
Read article →This corrects and sharpens the emphasis in the previous public copy, which mentioned landlord consent but didn't clearly warn about the risk of consent given for a different subtenant. Grounded in real LTB case outcomes observed via the public LTB Order Catalogue. A future enhancement to surface aggregate LTB outcome statistics is tracked separately (todo ltb-sublet-stats-feature) -- not part of this content entry.
Read article →Corrects the prior approach of hard-coding a member count directly into page copy (which then goes stale). This is a distinct data point from the "live count" feature referenced elsewhere in the tool-by-tool review -- that separate feature is a live count of posts available (e.g., "X short-term / X long-term listings in the last 60 days"), not a membership count, and should be built as a real analytics-backed feature, not knowledge content.
Read article →Removes the old fixed "reviews take about 48 hours" promise (this turnaround-time policy applies broadly, not just here -- no page should promise a fixed review time). Adds the new Community Team section, and reframes any turnaround expectation as a volunteer-capacity/funding-support message rather than an SLA. Member-count claims ("149K+ Members Strong") from the old copy should be refreshed/verified before publish, not carried over unchanged.
Read article →Version 2 adds disclosure of Anthropic (Claude API) as a real, live third-party sub-processor for FIKI Public chat messages, now that the LLM architecture decision (2026-09-02) is final and shipped -- version 1 only described a hypothetical future interaction record. All other sections carried forward unchanged from v1.
Read article →Retains the transparent methodology structure from the legacy page, but removes the unverified "140,000+ members" claim (superseded by the TOHS Community Size entry) and the specific YoY "September Surge" anecdote (kept general). Adds the minimum-sample-size suppression rule (5 listings per 120-day window) -- this was the open question flagged in the original triage and is now resolved.
Read article →Directly informed by real moderation decline patterns documented in docs/TOHS-Declined-Posts-Reasons-Sheet.md (category + feedback language only -- no names or raw post text retained per privacy handling rule).
Read article →