CorpusKit is an open source portal for finding, questioning and exploring a research collection. Every answer stays connected to the sources and passages that support it.
+ See the portal at work +Open source under Apache 2.0
Inspect, run, change and contribute
Browse · Search · Ask · Check · Map
+A cited answer is a claim with its working attached. Follow one claim from the answer back to the passage that supports it.
+Meadows recovered to near their pre-flood extent within three growing seasons, though recovery was slower where winter turbidity stayed above the long-term median 2.
+Sites where mean winter turbidity remained above the long-term median showed significantly slower recovery of seagrass extent over the two years following the floods. At these sites, light at the canopy fell below the minimum requirement for Zostera muelleri on 63 per cent of monitored days.
+ matched passage · page 41 +People arrive differently – with a question, a half-remembered report, a topic to browse or a hunch that two things are connected. A portal keeps all of those routes open.
+01Answers stream in with numbered citations and plain-language confidence. Deep research maps a broad question into focused sub-questions before answering.
+ + +Asked across the whole collection
+Shaded approaches and external blinds can reduce heat before it reaches the building. Plans should also identify a cooler internal room and set clear thresholds for changing how a space is used.
+The sources suggest that these changes work best when they are paired with local heat procedures, but they do not compare every building type.
+Recovery was slower where mean winter turbidity stayed above the long-term median. Reduced light at the canopy is the documented pathway.
+…sites where mean winter turbidity remained above the long-term median showed significantly slower recovery…
+…bank erosion in the upper catchment contributed an estimated two thirds of the fine sediment load reaching the estuary…
+Estuarine seagrass condition assessment 2019 to 2023
+Five years of condition monitoring across five estuaries, covering extent, density and light availability.
+ +Catchment sediment sources after the 2022 floods
+Traces fine sediment reaching the estuary to its catchment sources and ranks management options.
+ +Turbidity and light limitation in flood-affected estuaries
+Links elevated winter turbidity after floods to reduced light at the seagrass canopy and slower recovery.
+ +Recreational water quality guidelines review
+Reviews the thresholds behind recreational water quality guidance and the monitoring evidence supporting them.
+ +The application code is published under the Apache 2.0 licence. Clone it, connect a collection and run the portal on infrastructure you choose and manage.
+The repository holds the application, shared types, retrieval integration, tests, build tasks and deployment configuration – the same code that serves the live portals, with documented local setup and container configuration.
+One boundary matters when you plan a deployment: content storage and retrieval run on a connected knowledge service, and a deployment needs its own account with one. The Apache 2.0 licence covers the CorpusKit application code; connected services and the research material itself have their own terms.
+$ git clone https://github.com/corpuskit/corpuskit.git
+$ cd corpuskit
+$ cp .env.example .env # knowledge service account
+$ deno task devEvery change lands through a pull request. Typechecking, linting, formatting, tests and a full build run on each one, and a red check does not merge. What deploys is what was reviewed.
+The same gate applies to maintainers and first-time contributors, which keeps the standard visible instead of implied.
+CorpusKit is an open source research portal. Connect a research collection and people can search it, question it, browse its library and follow how the work connects – with every answer tied to passages they can open and check.
+ +Ask a question and the portal answers from the collection – streamed as it is produced, with numbered citations, follow-up questions and a plain statement of how well the sources support it. Each citation opens the passage it rests on, so checking a claim takes one click, and what you get is the exact lines from the research source.
+Across the trials this collection holds, cool roof coatings lowered peak indoor temperatures by 2 to 4 °C in uninsulated buildings, with the benefit narrowing to about 1 °C where ceiling insulation was already in place. The effect was strongest during extended heat, when coated roof surfaces ran up to 20 °C cooler than dark ones. Measured savings on cooling energy varied widely with building type and occupancy, so figures from any single site are best read as indicative.
+The retrieved sources support most of this answer – check the citations before relying on the exact figures.
+Research rarely hands over one clean answer, and a portal that pretends otherwise teaches its readers to stop checking. So CorpusKit marks its weak moments in plain sight – that candour is what makes the strong answers worth trusting.
+Below the relevance threshold for this search.
+Low confidence – use this answer as a lead. The retrieved passages only partly cover the question, so check the cited sources before relying on it.
+The collection does not hold enough to answer this question. Try a narrower question, or browse the topic to see what related work exists.
+Ask is one door into a collection. The rest of the portal is built for the days when you would rather look than ask.
+Results arrive ranked and scored, each carrying the passage that made it relevant, so you can judge a result before you open it. A short cited answer sits above the results by default; hide it and work from the results alone whenever that suits the job better.
+Hybrid, semantic and keyword modes, filters for topic and document kind, and watched searches that check for changed results daily.
+…each 10 per cent increase in canopy cover was associated with a 1.1 °C reduction in mean afternoon surface temperature along the monitored streets…
+…broad-crowned species delivered roughly twice the midday shade area of columnar forms by year ten…
+Every resource is presented as a research item with a clear title, a summary, key takeaways and notable quotes, whatever the underlying file was called. Open one and the original document sits beside its extracted text, its related resources, and a cited conversation held against that document alone.
+Search, sort and filter the whole catalogue, in grid or list view.
+Pairs street-level heat mapping with household interviews to show where extreme heat lands hardest, and which retrofits residents take up.
+ +Tracks establishment and upkeep costs across 14 installations, with a plain comparison against conventional roofing.
+ +A recorded seminar on shade planning for play spaces, with the speaker’s worked examples.
+ +The knowledge map shows what the research is about: the entities in it, the relationships between them, and a concept view of topics that occur together. Inspect a connection and the portal opens the resources behind it, so even the map answers to its sources.
+Search the map, filter it, and move between entity and concept views.
+CorpusKit is published under the Apache 2.0 licence, and the repository holds the whole application: shared types, retrieval integration, tests, build tasks and deployment configuration. Clone it, connect a collection and run the portal on infrastructure you choose.
+One deployment can serve several organisation-specific portals from configuration alone, each with its own name, identity, topics and collection. Content storage and retrieval run on a connected knowledge service, so a deployment needs an account with one; the application itself is yours to run, change and redistribute.
+ +git clone https://github.com/corpuskit/corpuskit.git +cd corpuskit +cp .env.example .env # add knowledge service credentials +deno task dev +Portal running at http://localhost:8790+
The short version. The repository documents the full setup, containers included.
+The project is looked after like infrastructure. Every change runs the same checks before it lands – typecheck, lint, tests and a build – and the repository says what exists now and what remains unfinished, so you can judge the state of things before committing to them.
+CorpusKit is developed in the open, and the people who run portals are often the people improving them. Code, design, documentation and tests all take contributions, and the standard is the same for everyone: a change says what it does, carries tests where behaviour changes, and passes the checks every other change passes.
+If you are new to the project, start small and concrete: report a problem with enough detail to reproduce it, improve a page of documentation you found wanting, or pick up an issue marked for first-time contributors. Not sure where something belongs? Open an issue and ask.
+ + +If your organisation runs one, start with a question you actually need answered, then open the citations behind whatever comes back. The habit of checking is the whole point.
+Clone the repository, connect a research collection and stand up a portal your organisation controls end to end.
+ + View the repository → +Report what is broken, improve what is unclear, and leave the project better than you found it.
+ Read the contributing guide → +CorpusKit is an open source portal for finding, questioning and exploring a research collection. Every answer stays connected to the sources and passages that support it.
+ See the portal at work +Open source under Apache 2.0
Inspect, run, change and contribute
Browse · Search · Ask · Check · Map
+Open a citation to read the matched passage. Confidence stays beside the answer, including when the sources only partly support it.
+Asked across the whole collection
+Shaded approaches and external blinds can reduce heat before it reaches the building. Plans should also identify a cooler internal room and set clear thresholds for changing how a space is used.
+The sources suggest that these changes work best when they are paired with local heat procedures, but they do not compare every building type.
+Matched passage: “Shade at entrances and external window protection reduce direct heat before it reaches occupied rooms…”
Matched passage: “Nominate a cooler internal room and document when regular activities should move or pause…”
Weak match · This resource mentions summer access but does not assess heat adaptation.
A practical review of passive cooling measures and heat response planning.
Report · 2025Thresholds, responsibilities and options for keeping public places available.
Guide · 2024A survey of building condition, access and seasonal use.
Study · 2024Numbered citations connect each claim to the research source behind it.
Search results show the excerpt that made each resource relevant.
Quality signals cover relevance, groundedness and context in plain language.
Weak matches are labelled, and unsupported questions can be declined.
The Library presents reports, webpages, recordings and other material as research items. Read a summary, note the key takeaways, open the original, or ask a cited question against one document.
+Maintenance plans are most useful when condition, access and seasonal demand are considered together.
+The complete application is published under the Apache 2.0 licence. One deployment can serve multiple organisation-specific portals, each shaped around its own research collection.
+$ git clone https://github.com/corpuskit/corpuskit.git
+$ cd corpuskit
+$ npm install
+$ npm run devOpen code deserves open working+
The repository shows what exists, how it is checked and where work remains.
+Developers, designers, researchers and documentation writers can report a problem or propose a change. Contributions are reviewed against the same standard as the product: clear behaviour, evidence where it matters, and tests for the change.
+Known limits belong in the open. A useful contribution can be a careful bug report, clearer documentation, a stronger test or a focused improvement to the portal.
+ Read the contribution guide +CorpusKit is an open source research portal. Connect a research collection and people can search it, ask questions that come back with numbered citations, browse the Library and follow the relationships between resources. The evidence stays within reach the whole time, so checking a claim is part of finding it.
+ +Published under the Apache 2.0 licence. Runs on your own infrastructure.
+Monitoring across five estuaries found that meadows returned to near their pre-flood extent within three growing seasons 1. Recovery was slower where winter turbidity stayed above the long-term median 2.
+ +Sites where mean winter turbidity remained above the long-term median showed significantly slower recovery of seagrass extent over the two years following the floods.
+product material, abridged
+A cited answer is a claim with its working attached. Follow one claim from the answer back to the passage that supports it.
+Meadows recovered to near their pre-flood extent within three growing seasons, though recovery was slower where winter turbidity stayed above the long-term median 2.
+Sites where mean winter turbidity remained above the long-term median showed significantly slower recovery of seagrass extent over the two years following the floods. At these sites, light at the canopy fell below the minimum requirement for Zostera muelleri on 63 per cent of monitored days.
+ matched passage · page 41 +Not every question has support in a collection, and pretending otherwise is how research tools lose trust. CorpusKit labels weak matches, states low confidence plainly and will answer with nothing rather than a confident guess.
+Administrators see the same candour. Knowledge-gap reporting shows what people asked that the collection could not answer, so the gaps become work rather than surprises.
+Do cormorant numbers affect seagrass recovery?
+No direct evidence found
+No passages in this collection directly answer this question. Try a narrower question, or browse the topic Estuary condition.
+People arrive differently – with a question, a half-remembered report, a topic to browse or a hunch that two things are connected. A portal keeps all of those routes open.
+Results are ranked resources, each showing the passage that made it relevant, with calibrated scores and filters for topic and document kind. Hybrid, semantic and keyword modes are a click apart.
+A short cited answer sits above the results by default. Hide it and work with the passages alone, summarise a set of results, or watch a search and hear when its results change.
+…sites where mean winter turbidity remained above the long-term median showed significantly slower recovery…
+…bank erosion in the upper catchment contributed an estimated two thirds of the fine sediment load reaching the estuary…
+Answers stream in with numbered citations, the sources behind them and suggested follow-ups. Answer quality reports relevance, groundedness and context, and confidence is stated in plain language rather than a score alone.
+Deep research takes a broad question and maps it into focused sub-questions before answering. Sessions can be saved, renamed and exported, so a line of enquiry can be picked up where it stopped.
+How has estuary condition changed since 2019, and what drove the change?
+Deep research · mapping the question
+Every resource carries a clear title, a summary, key takeaways and notable quotes, whatever the underlying file was called. Search, sort and filter the catalogue, in grid or list view.
+A resource page shows the original document, the extracted text, related resources and a conversation limited to that one document, so a question can be put to a single report instead of the whole collection.
+Estuarine seagrass condition assessment 2019 to 2023
+Five years of condition monitoring across five estuaries, covering extent, density and light availability.
+ +Catchment sediment sources after the 2022 floods
+Traces fine sediment reaching the estuary to its catchment sources and ranks management options.
+ +The entity view shows the things the research talks about and the relationships between them. The concept view shows which topics and document kinds occur together.
+Search the map, filter it, inspect a connection and open the resources behind it. The map is drawn from the collection, not laid over it, and it reflects the entities and relationships configured for each portal.
+A research portal earns trust slowly and loses it quickly. Manage treats the collection as something looked after, not loaded once.
+Administrators add files, text and webpages, register website sources and schedule synchronisation. Collection health finds what went wrong – failed extractions, bot-challenge pages, resources with almost no text – and drafts stay out of public retrieval until they are ready.
+Analysing the collection refreshes its topics, document kinds, suggested questions and the structure of the knowledge map as the research grows, so the portal keeps describing the collection it actually holds.
+The MCP connector lets an approved external research tool search the collection, request a cited answer, retrieve a document and browse the catalogue. Access is read-only and scoped to one portal.
+Access keys are issued by an administrator, shown once and revocable at any time. The credential for the underlying content service never leaves the server.
+Each portal has its own name, identity, topics, suggested questions and knowledge-map structure, served from configuration rather than separate branches of the application.
+The portals differ where their collections differ. The system underneath stays the same, which is what makes it maintainable.
+The application code is published under the Apache 2.0 licence. Clone it, connect a collection and run the portal on infrastructure you choose and manage.
+The repository holds the application, shared types, retrieval integration, tests, build tasks and deployment configuration – the same code that serves the live portals, with documented local setup and container configuration.
+One boundary matters when you plan a deployment: content storage and retrieval run on a connected knowledge service, and a deployment needs its own account with one. The Apache 2.0 licence covers the CorpusKit application code; connected services and the research material itself have their own terms.
+# clone, configure, run
+git clone https://github.com/corpuskit/corpuskit
+cd corpuskit
+cp .env.example .env # knowledge service account
+deno task devlocal setup and container configuration are documented in the repository
+Every change lands through a pull request. Typechecking, linting, formatting, tests and a full build run on each one, and a red check does not merge. What deploys is what was reviewed.
+The same gate applies to maintainers and first-time contributors, which keeps the standard visible instead of implied.
+CorpusKit is built by developers, designers, researchers and documentation writers working from the same repository that runs the portals. Small contributions are genuinely useful: a careful bug report, a fix with a test, a clearer paragraph of documentation.
+Open issues are labelled so you can tell what is ready to pick up, what is under discussion and what remains unfinished. Every change runs the same checks as a maintainer's, and a maintainer reads everything before it lands.
+Search a research collection, ask cited questions and open the passages behind each answer. CorpusKit keeps useful findings connected to the material that supports them.
+ +Start with a question, a known report, a topic or a connection. The research stays within reach as you move.
+CorpusKit places the answer, its confidence and the relevant passages in one line of sight. Select a citation to inspect what supports that part of the answer.
+Across the retrieved sources, reopening tidal connections is associated with improved water exchange and the return of saltmarsh vegetation in some modified wetlands .
+The evidence also shows that results depend on site elevation, sediment movement and the condition of existing channels . The collection does not provide a direct comparison of long-term outcomes across every restoration method .
+Monitoring showed that the reopened channels changed the frequency and reach of tidal exchange across the study sites.
+Saltmarsh vegetation returned in areas where water movement improved and elevation remained suitable for establishment.
+The report recommends continued monitoring because early vegetation response does not establish long-term resilience.
+Site response varied across the reviewed restoration projects.
+Elevation, sediment supply and the condition of existing channels were recurring influences on the extent and pace of recovery.
+The review cautions against applying a single expected outcome across sites with different physical settings.
+The note identifies differences in monitoring periods and measures across the available project reports.
+No direct evidence was found that compares long-term outcomes across every restoration method in the collection.
+Treat this result as a lead and check the sources before relying on it.
+Each citation links to the research source, not a detached summary.
High, moderate, low and unscored states stay close to the answer they qualify.
Weak matches and missing direct evidence remain visible when the collection cannot support more.
A portal supports different research habits without separating them into different systems.
+Compare ranked resources, matched passages and relevance. Switch between hybrid, semantic and keyword search.
+Save a continuing cited conversation, follow a suggested question or break broad work into focused questions.
+Filter the full catalogue and open the original file, extracted text, transcript or related resources where available.
+The knowledge map shows entities, relationships and topic overlaps configured for a portal. Inspect a connection, then open the resources behind it.
+ See how the structure is maintained +Manage gives content stewards one place to add research, check processing, hold drafts, maintain the taxonomy and see where the collection needs attention.
+Register sources and run or schedule synchronisation when published research changes.
Find failed ingests, bot-challenge pages and resources with very little extracted text.
Keep a resource as a draft and outside public retrieval until it is ready.
Analyse the connected material to update topics, document kinds, suggested questions and map dimensions.
The CorpusKit application is published under the Apache 2.0 licence. The repository includes the application, shared types, retrieval integration, tests, build tasks and deployment configuration.
+ +CorpusKit connects to a separate knowledge service for content storage and retrieval. Running the application requires an account with that service. Infrastructure, connected services and research material can have their own costs, licences and terms.
+Design bake-off · 1 September 2026
+Two briefs, two builders, four pages. Open each full screen; check desktop and 390 px.
+ + +