Scope + data · the ingest boundary

The boundary is a setting your own teams own.

What Take Interest reads is configured by Crestline IT and compliance at install, written down, and open to review any time. The controlled technical data never enters. This page is where the line lives.

DATUM

Threaded sources 5 · ON

Never-touched sources 4 · LOCKED OFF

Boundary set by IT + COMPLIANCE

Take Interest does not choose what it reads. Your IT and compliance teams set the boundary at install and can change or revoke it at any time. Every change lands in the log below.

What crosses the line, and what never does

Threaded

COORDINATION METADATA

Non-controlled coordination signals. Timing, ownership, status, and narrative cadence · never engineering content.

Calendars + customer-visit cadence ON

Internal ops chat (non-engineering) ON

Customer-visit + relationship threads ON

Industry-event prep ON

AIP reporting narrative (timing + status, not content) ON

Follow-up status: record IDs, owners, dates, dispositions ON

Never touched

CONTROLLED · OUT OF SCOPE

Controlled technical data and CUI. It stays inside your existing AS9100 systems and reporting paths. None of it is readable here.

CAD, drawings, geometries NEVER

Program-name technical data NEVER

Specs, BOMs, fastener patterns NEVER

Quality-record content (FAI / NCR analysis text) NEVER

Cost-accounting / DCAA detail NEVER

Anything CUI NEVER

How a quality follow-up reads

A nonconformance record shows up here as its ID, owner, open date, due date, current step, and disposition tag · enough to flag that it is aging or unlinked. The analysis text, the characteristic results, and the drawing stay in your quality system. Take Interest sees that a record exists and where it stands, never what it says.

Per-source ingest controls

Set by IT + compliance · changes are logged below

Threaded sources can be turned off here. Controlled sources are locked off and cannot be turned on from this product at all.

Microsoft Outlook · mail metadata, no attachments Threaded

Microsoft Teams · non-engineering channels Threaded

Calendar · visit + event cadence Threaded

Travel app · itinerary timing only Threaded

AIP reporting · narrative timing + status Threaded

CAD · drawings, geometries Locked off

PLM · system of record, stays system of record Locked off

Quality records · FAI / NCR content Locked off

Cost accounting · DCAA detail Locked off

The locked sources are enforced by configuration, not by this page. Turning a threaded source off takes effect at the next sync; nothing is ever read from a source that is off.

Scope change log

Who changed the boundary, and when

Every change to the ingest boundary is recorded with the person and the time. The log is append-only and exportable for your compliance review. Flip a source above and the change lands here.

2026-05-12 · 09:41 · IT · install team Quality records confirmed locked off at install OFF

2026-05-12 · 09:41 · IT · install team CAD + PLM confirmed locked off at install OFF

2026-05-12 · 09:40 · Compliance · ITAR review Ingest boundary approved · coordination metadata only APPROVED

2026-05-12 · 09:38 · IT · install team Outlook · Teams · Calendar · Travel · AIP reporting added to scope THREADED

Auditable any time

You can ask for the current boundary and its full change history whenever you want, and hand it straight to a compliance review. The boundary is written down, the log is append-only, and the controlled data stays where it lives today.

Coordination metadata only · the controlled technical data never enters Take Interest.