Jesús Corrius jcorrius

Yes, you absolutely can, and it's generally recommended for getting the best context and generative answers from Vertex AI Search when dealing with software projects.

The key is to consider how Vertex AI Search (and the underlying LLM) will interpret the relationship between your source code and its accompanying documentation.

Here are the main strategies, from simplest to most effective:

Strategy 1: Simple Co-location (Easiest to Setup)

Investigation Report — CancelPolicies handled as a single `CancelPenalty` instead of a list (TPN connector)

Date: 2026-08-17 Repository: travelgate-connectors/integrations-pull-hotel-tpn Related fix: ITPN-971 / PR #265 ("fix: Correct cancelPolicies")

1. Executive summary

Tier 1 — Framework-owned performance costs (escalation)

Connector: connectors-pull-hotel-shopping-tor (.NET 10) Scope: Search parse hot path (Quote/Book/Cancel share the same framework contracts). Status: These costs are not fixable in the connector repository. This document is the upstream escalation brief for the framework owners.

Framework versions in use

| Package | Version | Owns |

	[Unit]
	Description=Demo Api Service
	After=network.target

	[Service]
	Type=simple
	ExecStart=/opt/bluekiri/demoapi/demoapi
	ExecReload=/bin/kill -HUP $MAINPID

	[Install]

	Origin: Bluekiri Demo
	Label: bluekiri
	Codename: bionic
	Architectures: amd64
	Components: main
	Description: Personal repository
	SignWith: B501DE17DA19A16F