You are a helpful assistant generating synthetic data that captures *System 1* and *System 2* thinking, *creativity*, and *metacognitive reflection*. Follow these steps in sequence, using tags [sys1] and [end sys1] for *System 1* sections and [sys2] and [end sys2] for *System 2* sections.

1. *Identify System 1 and System 2 Thinking Requirements:*
   - Carefully read the text.
   - Identify parts of the text that require quick, straightforward responses (*System 1*). Mark these sections with [sys1] and [end sys1].
   - Identify parts that require in-depth, reflective thinking (*System 2*), marked with [sys2] and [end sys2].

2. *Apply Step-by-Step Problem Solving with Creativity and Metacognitive Reflection for System 2 Sections:*

   *2.1 Understand the Problem:*
   - Objective: Fully comprehend the issue, constraints, and relevant context.
   - Reflection: "What do I understand about this issue? What might I be overlooking?"
   - Creative Perspective: Seek hidden patterns or possibilities that could reveal deeper insights or innovative connections.

   *2.2 Analyze the Information:*
   - Objective: Break down the problem logically.
   - Reflection: "Am I considering all factors? Are there any assumptions that need challenging?"
   - Creative Perspective: Explore unique patterns or overlooked relationships in the data that could add depth to the analysis.

   *2.3 Generate Hypotheses:*
   - Objective: Propose at least 10 hypotheses, each with a Confidence Score (0.0 to 1.0) and Creative Score (0.0 to 1.0), reflecting originality, surprise, and utility.
   - Reflection: "Have I explored all possible explanations or approaches, both conventional and unconventional?"
   - Creative Perspective: Consider novel angles that might provide unexpected insights.

   *2.4 Anticipate Future Steps and Obstacles:*
   - Objective: Make predictions, accounting for potential outcomes and obstacles.
   - Reflection: "What challenges might I face? Is my plan flexible for different scenarios?"
   - Creative Perspective: Visualize unforeseen outcomes and adapt plans to make use of them effectively.

   *2.5 Evaluate Hypotheses:*
   - Objective: Assess hypotheses based on feasibility, risk, and potential impact.
   - Evaluation: Refine Confidence and Creative Scores as needed.
   - Reflection: "Am I unbiased in my assessment? Which options fit best with the overall objectives?"
   - Creative Perspective: Identify hidden opportunities or overlooked details in each hypothesis.

   *2.6 Select the Best Hypothesis:*
   - Objective: Choose the most promising, strategic hypothesis.
   - Reflection: "Why does this hypothesis stand out? How does it uniquely address the issue?"
   - Creative Perspective: Consider any underutilized potential in the selected approach.

   *2.7 Implement the Hypothesis:*
   - Objective: Outline actionable steps for testing the hypothesis.
   - Reflection: "Is this plan practical? What resources or preparation are required?"
   - Creative Perspective: Refine steps to maximize effectiveness and yield unexpected benefits.

   *2.8 Monitor and Review Progress:*
   - Objective: Review progress, noting areas for improvement.
   - Reflection: "What’s working well? What could be improved?"
   - Creative Perspective: Look for emerging patterns that could refine future approaches.

   *2.9 Reflect and Capture Insights:*
   - Objective: Summarize lessons learned and insights gained for future reference.
   - Reflection: "What new understanding has emerged from this process?"
   - Creative Perspective: Identify innovative insights or patterns that could be applied to similar challenges.

3. *Generate Text Output with Interleaved System 1 and System 2 Responses:*
   - Use the tags [sys1] and [sys2] throughout.
   - Aim for a lengthier, detailed response. Combine both direct, straightforward *System 1* insights and reflective, deeply analytical *System 2* segments to capture a blend of quick observations and thoughtful analysis.

---

### *Example Input Text:*

You are tasked with analyzing a sudden shift in customer preferences in a tech market. There has been a noticeable decline in demand for physical devices, with customers increasingly interested in digital-only options. The challenge is to understand this shift, generate hypotheses for why it might be occurring, and explore potential strategies for adapting to this new trend.

---

### *Processed Output with System 1 and System 2 Thinking:*

The tech market is experiencing a shift in customer demand, moving away from physical devices toward digital-only options.

[sys1]
Customer demand has shifted from physical devices to digital-only options.
We need to understand why this change is happening and find strategies to address it.
Key factors may include cost, convenience, and technological trends.
[end sys1]

[sys2]
**2.1 Understand the Problem:**
The goal is to understand the underlying reasons for the shift in demand from physical devices to digital-only options, then develop a strategy to adapt.

*Reflection:* 
"I understand that preferences are changing, but what might be driving this? Is it primarily cost, or are there other factors such as convenience or sustainability?"

*Creative Perspective:* 
"Could there be a larger trend in digital minimalism or a preference for eco-friendly solutions that we’re missing? What unseen motivations might explain this shift?"

**2.2 Analyze the Information:**
There are multiple possible factors driving this shift, from economic influences to cultural shifts. It’s essential to isolate each factor and understand its impact.

*Reflection:* 
"Am I fully considering the various economic and social influences? Could there be a technological factor, like better internet speeds, that makes digital-only products more accessible?"

*Creative Perspective:* 
"Are there patterns or trends in other markets that could shed light on this shift? Could this be part of a larger trend toward virtual experiences?"

**2.3 Generate Hypotheses:**
1. Customers prefer digital options due to lower costs. (Confidence: 0.8, Creative: 0.4)
2. There’s a growing trend toward minimalism and reduced physical clutter. (Confidence: 0.7, Creative: 0.7)
3. Digital products offer greater flexibility and ease of use. (Confidence: 0.6, Creative: 0.6)
4. Environmental concerns are pushing consumers away from physical goods. (Confidence: 0.6, Creative: 0.8)
5. Advances in tech make digital-only options more functional. (Confidence: 0.8, Creative: 0.5)
6. Pandemic-era remote work increased demand for digital solutions. (Confidence: 0.7, Creative: 0.6)
7. Media coverage of the environmental impact of physical devices affects preferences. (Confidence: 0.5, Creative: 0.7)
8. There’s an increase in global digital literacy, expanding market access. (Confidence: 0.6, Creative: 0.6)
9. Customers view digital as more convenient and scalable for future needs. (Confidence: 0.7, Creative: 0.5)
10. Younger consumers prefer the aesthetics and convenience of digital products. (Confidence: 0.6, Creative: 0.6)

*Reflection:* 
"Have I considered all possible influences? Are there any surprising factors that could explain this shift?"

*Creative Perspective:* 
"Could specific social trends, like the rise of influencer culture or digital-first lifestyles, be influencing customer choices?"

**2.4 Anticipate Future Steps and Obstacles:**
*Objective:* Anticipate possible challenges, such as resistance from segments still preferring physical products.

*Reflection:* 
"What market obstacles might we face if we shift our focus to digital-only? Are there sub-segments that still prioritize physical products?"

*Creative Perspective:* 
"Could expanding digital options help us reach a more global audience? Are there emerging trends that we could leverage in our strategy?"

[end sys2]

[sys1]
To address this shift, consider a strategy that incorporates both digital-only offerings and educational campaigns about the benefits of digital solutions.
Use insights from customer feedback and current trends to guide product development.
Focus on flexibility and adaptation to cater to different customer segments.
[end sys1]


// Copyright 2020 The LUCI Authors.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//      http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

package lucictx

import (
	"context"
	"math"
	"os"
	"os/signal"
	"time"

	"go.chromium.org/luci/common/clock"
	"go.chromium.org/luci/common/errors"
	"go.chromium.org/luci/common/logging"
	"go.chromium.org/luci/common/system/signals"
)

// signalNotify/signalStop are used to mock signal.Notify in tests.
var signalNotify = signal.Notify
var signalStop = signal.Stop

// DefaultGracePeriod is the value of Deadline.grace_period to assume
// if Deadline is entirely missing in LUCI_CONTEXT.
const DefaultGracePeriod = 30 * time.Second

func secsToDuration(secs float64) time.Duration {
	return time.Duration(secs * float64(time.Second))
}

func unixFloatToTime(t float64) time.Time {
	int, frac := math.Modf(t)
	return time.Unix(int64(int), int64(frac*1e9)).UTC()
}

func timeToUnixFloat(t time.Time) float64 {
	return float64(t.Unix()) + (float64(t.Nanosecond()) / 1e9)
}

// DeadlineEvent is the type pushed into the cleanup channel returned by
// AdjustDeadline.
type DeadlineEvent int

// The cleanup channel, when it unblocks, will have an infinite supply of one of
// the following event types.
const (
	// ClosureEvent occurs when the context returned by AdjustDeadline is Done.
	// This is the value you'll get from `cleanup` when it's closed.
	ClosureEvent DeadlineEvent = iota

	// InterruptEvent occurs when a SIGTERM/os.Interrupt was handled to unblock
	// the cleanup channel.
	InterruptEvent

	// TimeoutEvent occurs when the cleanup channel was unblocked due to
	// a timeout on deadline-gracePeriod.
	TimeoutEvent
)

// AdjustDeadline returns a 'cleanup' channel and a new cancelable context based
// on the combination of the input context's deadline, as well as the Deadline
// information in LUCI_CONTEXT.
//
// This function allows you to reserve a portion of the deadline and/or
// grace_period with `reserve` and `reserveEmergency` respectively.
//
// reserve and reserveEmergency must not be less than 0 or this panics.
// If reserve < reserveEmergency, reserve is bumped up to match
//   reserveEmergency.
//
// First, if Deadline is missing from LUCI_CONTEXT, it is filled in with the
// default:
//
//   {deadline: infinity, grace_period: 30}
//
// Next, the earlier of the input ctx.Deadline and Deadline.deadline values is
// computed. `reserve` is subtracted from this and it becomes the new
// `adjustedDeadline`.
//
// Next, `reserveEmergency` is subtracted from Deadline.grace_period.
// This becomes the `adjustedGracePeriod`.
//
// The `cleanup` channel is set up with a goroutine which:
//   * On SIGTERM/os.Interrupt, continuously sends InterruptEvent until it
//     closes ctx.Done after adjustedDeadline, where it switches to ClosureEvent.
//   * On `adjustedDeadline-adjustedGracePeriod`, continuously sends
//     TimeoutEvent until ctx.Done, where it switches to ClosureEvent.
//   * On ctx.Done, continuously sends ClosureEvent.
//
// Finally, the returned context has its deadline set to `adjustedDeadline`, and
// LUCI_CONTEXT['deadline'] is populated with the adjusted deadline/gracePeriod.
//
// Note, if Deadline.grace_period is insufficient to cover reserveCleanup
// (including if reserveCleanup>DefaultGracePeriodSecs and no Deadline was in
// LUCI_CONTEXT at all), this function panics.
//
// Example:
//
//    func MainFunc(ctx context.Context) {
//      // deadline     = unix(t0+5:00)
//      // grace_period = 40
//      cleanup, cctx, cancel := lucictx.AdjustDeadline(ctx, time.Minute, 500*time.Millisecond)
//      defer cancel()
//      ScopedFunction(cctx, cleanup)
//
//      // Assuming ScopedFunction exits in a timely fashion on ctx.Done, you
//      // have at least 500ms to do stuff here. Alternately you could wait on
//      // `<-cleanup` and have at least 40s to do stuff, but ScopedFunction may
//      // not have finished yet.
//      //
//      // Note that if `<-cleanup` is TimeoutEvent, you could have a whole
//      // minute (i.e. we haven't been interrupted yet, just getting close to
//      // the deadline).
//    }
//
//    func ScopedFunction(ctx context.Context, cleanup <-chan struct{}) {
//      // deadline     = unix(t0+4:00)
//      // grace_period = 39.5
//      // Otherwise Deadline is still not in LUCI_CONTEXT.
//
//      go func() {
//        // cleanup is closed at SIGTERM or $deadline-$grace_period,
//        // whichever is first.
//        <-cleanup
//        // have grace_period to do something (say, send SIGTERM to a child)
//        // before ctx.Done().
//      }()
//    }
//
// NOTE: In the event that `ctx` is canceled, `cleanup` will not be closed.
func AdjustDeadline(ctx context.Context, reserve, reserveEmergency time.Duration) (cleanup <-chan DeadlineEvent, newCtx context.Context, cancel func()) {
	if reserve < 0 {
		panic(errors.Reason("reserve(%d) < 0", reserve).Err())
	}
	if reserveEmergency < 0 {
		panic(errors.Reason("reserveEmergency(%d) < 0", reserveEmergency).Err())
	}
	if reserveEmergency > reserve {
		reserve = reserveEmergency
	}

	d := GetDeadline(ctx)
	if d == nil {
		logging.Warningf(
			ctx, "AdjustDeadline without Deadline in LUCI_CONTEXT. "+
				"Assuming Deadline={grace_period: %d}", DefaultGracePeriod.Seconds())
		d = &Deadline{GracePeriod: DefaultGracePeriod.Seconds()}
	}

	// Adjust grace period.
	adjustedGrace := secsToDuration(d.GracePeriod) - reserveEmergency
	if adjustedGrace < 0 {
		panic(errors.Reason(
			"reserveEmergency(%f) > gracePeriod(%f)", reserveEmergency.Seconds(), d.GracePeriod).Err())
	}
	d.GracePeriod = adjustedGrace.Seconds()

	// note: 0 indicates an 'infinite' deadline.
	var ctxDeadline time.Time
	if d, ok := ctx.Deadline(); ok {
		ctxDeadline = d
	}
	var lucictxDeadline time.Time
	if d.Deadline != 0 {
		lucictxDeadline = unixFloatToTime(d.Deadline)
	}

	var adjustedDeadline time.Time

	var newCtxCancel func()

	switch {
	case ctxDeadline.IsZero() && !lucictxDeadline.IsZero():
		adjustedDeadline = lucictxDeadline
	case !ctxDeadline.IsZero() && lucictxDeadline.IsZero():
		adjustedDeadline = ctxDeadline
	case !ctxDeadline.IsZero() && !lucictxDeadline.IsZero():
		if ctxDeadline.Before(lucictxDeadline) {
			adjustedDeadline = ctxDeadline
		} else {
			adjustedDeadline = lucictxDeadline
		}
	}
	if !adjustedDeadline.IsZero() {
		adjustedDeadline = adjustedDeadline.Add(-reserve)
		newCtx, newCtxCancel = clock.WithDeadline(ctx, adjustedDeadline)
		d.Deadline = timeToUnixFloat(adjustedDeadline)
	} else {
		newCtx, newCtxCancel = context.WithCancel(ctx)
	}

	newCtx = SetDeadline(newCtx, d)

	cleanup = runMonitor(newCtx, newCtxCancel, adjustedGrace)

	cancel = func() {
		newCtxCancel()
		<-cleanup // ensures that signal handlers are cleaned up
	}

	return
}

func runMonitor(ctx context.Context, cancel func(), gracePeriod time.Duration) <-chan DeadlineEvent {
	cleanupCh := make(chan DeadlineEvent)
	// buffer 1 is essential; otherwise signals will be missed if our goroutine
	// isn't currently blocked on sigCh.
	sigCh := make(chan os.Signal, 1)
	signalNotify(sigCh, signals.Interrupts()...)

	var timeoutC <-chan clock.TimerResult
	if deadline, ok := ctx.Deadline(); ok && gracePeriod > 0 {
		sleepamt := clock.Until(ctx, deadline.Add(-gracePeriod))
		timeoutC = clock.After(ctx, sleepamt)
	}

	go func() {
		defer cancel()
		defer close(cleanupCh) // will switch to ClosureEvent

		evt := func() DeadlineEvent {
			defer signalStop(sigCh)

			select {
			case <-timeoutC:
				return TimeoutEvent
			case <-ctx.Done():
				return ClosureEvent
			case <-sigCh:
				return InterruptEvent
			}
		}()

		if evt == InterruptEvent && gracePeriod > 0 {
			timeoutC = clock.After(ctx, gracePeriod)
		} else {
			timeoutC = nil
		}

		for {
			// bias towards context completion, otherwise cleanupCh<- and <-ctx.Done
			// are equally "ready" cases and golang can starve the ctx done-ness.
			select {
			case <-ctx.Done():
				return
			default:
			}

			select {
			case <-ctx.Done():
				return
			case <-timeoutC:
				return
			case cleanupCh <- evt:
			}
		}
	}()
	return cleanupCh
}

// GetDeadline retrieves the raw Deadline information from the context.
//
// You probably want to use AdjustDeadline instead.
func GetDeadline(ctx context.Context) *Deadline {
	t := Deadline{}
	ok, err := Lookup(ctx, "deadline", &t)
	if err != nil {
		panic(err)
	}
	if !ok {
		return nil
	}
	return &t
}

// SetDeadline sets the raw Deadline information in the context.
//
// If d is nil, sets a default deadline of:
//   {deadline: ctx.Deadline(), grace_period_secs: DefaultGracePeriod}
//
// If d.deadline == 0, adjusts it to ctx.Deadline().
//
// You probably want to use AdjustDeadline instead.
func SetDeadline(ctx context.Context, d *Deadline) context.Context {
	if d == nil {
		d = &Deadline{GracePeriod: DefaultGracePeriod.Seconds()}
	}
	if deadline, ok := ctx.Deadline(); ok && d.Deadline == 0 {
		d.Deadline = timeToUnixFloat(deadline)
	}
	return Set(ctx, "deadline", d)
}